Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/pages/get-started/gs-web-api-request.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ HTTP header | Description | Syntax
--- | --- | ---
`Authorization` | Required, except for calls made on behalf of a guest. Specifies the authentication token that proves you as the owner of a customer, admin, or integration account. You specify the token in the `Authorization` request header with the `Bearer` HTTP authorization scheme. | `Authorization: Bearer <TOKEN>` <br/><br/>`<TOKEN>` is the authentication token returned by the token service. See [Authentication](./authentication/).
`Accept` | Optional. Specifies the format of the response body. Default is `JSON`. | `Accept: application/<FORMAT>` <br/><br/>`<FORMAT>` is either `JSON` or `XML`.
`X-Adobe-Company` | Optional. The Company ID scope for the request when a company user is assigned to more than one company. If this value is omitted, the user's default company scope is used. Use the `/V1/customers/:customer_id` call to get the company ids associated with a company user account.| `<company_id>`
`X-Adobe-Company` | Optional. The Company unique ID scope for the request when a company user is assigned to more than one company. If this value is omitted, the user's default company scope is used. Use the `/V1/customers/:customer_id` call to get the company ids associated with a company user account.| `<company_uid>`
`Content-Type` | Required for operations with a request body. Specifies the format of the request body. | `Content-Type:application/<FORMAT>` <br/><br/>`<FORMAT>` is either `JSON` or `XML`.
&#8203;<Edition name="saas" /> `Store` | The store view code on which to perform the request. The value can be `all`, `default`, or the code that is defined when a store view is created. In Adobe Commerce as a Cloud Service, this is the only way to specify a store view code in a REST call. | `<store_view_code>`
`X-Captcha` | A shopper-entered CAPTCHA value. It is required when a shopper enters a CAPTCHA value on the frontend, unless an integration token is provided. Forms requiring CAPTCHA values are configured at **Stores** > **Configuration** > **Customers** > **Customer Configuration** > **CAPTCHA** > **Forms**. | String
Expand Down
2 changes: 1 addition & 1 deletion src/pages/graphql/usage/headers.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ The application accepts the following headers in a GraphQL request:
Header name | Value | Description
--- | --- | ---
`Authorization` | `Bearer <authorization_token>` | A customer or admin token. [Authorization tokens](authorization-tokens.md) describes how to generate tokens.
`X-Adobe-Company` | `<company_id>` | The Company ID scope for the request that identifies the company scope when a company user is assigned to more than one company. If this value is omitted, the user's default company scope is used. Use the [Get customer query](../schema/customer/queries/customer.md) to retrieve information about the companies assigned to a company user account.
`X-Adobe-Company` | `<company_uid>` | The Company ID scope for the request that identifies the company scope when a company user is assigned to more than one company. If this value is omitted, the user's default company scope is used. Use the [Get customer query](../schema/customer/queries/customer.md) with `company_id` in the response to retrieve information about the companies assigned to a company user account.
`Content-Currency` | A valid currency code, such as `USD` | This header is required only if the currency is not the store view's default currency.
`Content-Type` | `application/json` | Required for all requests.
`Preview-Version` | A timestamp (seconds since January 1, 1970). | Use this header to query products, categories, price rules, and other entities that are scheduled to be in a campaign (staged content). Staging is supported in Adobe Commerce only.
Expand Down
Loading