Creates a Merchant Center sub-account.

Scopes

You will need authorization for the https://www.googleapis.com/auth/content scope to make a valid call.

If unset, the scope for this method defaults to https://www.googleapis.com/auth/content. You can set the scope for this method like this: content2 --scope <scope> accounts insert ...

Required Scalar Argument

  • <merchant-id> (string)
    • The ID of the managing account. This must be a multi-client account.

Required Request Value

The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.

For example, a structure like this:

Account:
  adult-content: boolean
  business-information:
    address:
      country: string
      locality: string
      postal-code: string
      region: string
      street-address: string
    customer-service:
      email: string
      phone-number: string
      url: string
    korean-business-registration-number: string
    phone-number: string
  google-my-business-link:
    gmb-email: string
    status: string
  id: string
  kind: string
  name: string
  reviews-url: string
  seller-id: string
  website-url: string

can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.

  • -r . adult-content=true
    • Indicates whether the merchant sells adult content.
  • business-information.address country=voluptua.
    • CLDR country code (e.g. "US"). This value cannot be set for a sub-account of an MCA. All MCA sub-accounts inherit the country of their parent MCA.
  • locality=at
    • City, town or commune. May also include dependent localities or sublocalities (e.g. neighborhoods or suburbs).
  • postal-code=sanctus
    • Postal code or ZIP (e.g. "94043").
  • region=sed
    • Top-level administrative subdivision of the country. For example, a state like California ("CA") or a province like Quebec ("QC").

  • street-address=amet.

    • Street-level part of the address.

  • ..customer-service email=takimata

    • Customer service email.
  • phone-number=amet.
    • Customer service phone number.

  • url=duo

    • Customer service URL.

  • .. korean-business-registration-number=ipsum

  • phone-number=gubergren

    • The phone number of the business.

  • ..google-my-business-link gmb-email=lorem

    • The GMB email address of which a specific account within a GMB account. A sample account within a GMB account could be a business account with set of locations, managed under the GMB account.

  • status=gubergren

    • Status of the link between this Merchant Center account and the GMB account. Acceptable values are: - "active" - "pending"

  • .. id=eos

    • Required for update. Merchant Center account ID.
  • kind=dolor
    • Identifies what kind of resource this is. Value: the fixed string "content#account"
  • name=ea
    • Required. Display name for the account.
  • reviews-url=ipsum
    • [DEPRECATED] This field is never returned and will be ignored if provided.
  • seller-id=invidunt
    • Client-specific, locally-unique, internal ID for the child account.
  • website-url=amet
    • The merchant's website.

About Cursors

The cursor position is key to comfortably set complex nested structures. The following rules apply:

  • The cursor position is always set relative to the current one, unless the field name starts with the . character. Fields can be nested such as in -r f.s.o .
  • The cursor position is set relative to the top-level structure if it starts with ., e.g. -r .s.s
  • You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify -r struct.sub_struct=bar.
  • You can move the cursor one level up by using ... Each additional . moves it up one additional level. E.g. ... would go three levels up.

Optional Output Flags

The method's return value a JSON encoded structure, which will be written to standard output by default.

  • -o out
    • out specifies the destination to which to write the server's result to. It will be a JSON-encoded structure. The destination may be - to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.

Optional Method Properties

You may set the following properties to further configure the call. Please note that -p is followed by one or more key-value-pairs, and is called like this -p k1=v1 k2=v2 even though the listing below repeats the -p for completeness.

  • -p dry-run=boolean
    • Flag to simulate a request like in a live environment. If set to true, dry-run mode checks the validity of the request and returns errors (if any).

Optional General Properties

The following properties can configure any call, and are not specific to this method.

  • -p $-xgafv=string

    • V1 error format.

  • -p access-token=string

    • OAuth access token.

  • -p alt=string

    • Data format for response.

  • -p callback=string

    • JSONP

  • -p fields=string

    • Selector specifying which fields to include in a partial response.

  • -p key=string

    • API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.

  • -p oauth-token=string

    • OAuth 2.0 token for the current user.

  • -p pretty-print=boolean

    • Returns response with indentations and line breaks.

  • -p quota-user=string

    • Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.

  • -p upload-type=string

    • Legacy upload protocol for media (e.g. "media", "multipart").

  • -p upload-protocol=string

    • Upload protocol for media (e.g. "raw", "multipart").