Adobe Commerce Magento Connector
Adobe Commerce (Magento) is an open-source e-commerce platform.
Use the Adobe Commerce component to manage the Products, Orders, Customers, and Transactions in an Adobe Commerce store.
API Documentation
This component was built using the Adobe Commerce REST API Overview.
Connections
API Access Key (Deprecated)
Authenticate with Adobe Commerce using an API Access Key and Secret.
This connection authenticates against the Adobe Commerce Marketplace Developer API, the portal used to submit and manage extensions. It does not authenticate against a merchant's store, so it cannot read or write store data such as orders, products, customers or transactions. Use the OAuth 1.0a connection for store data.
The Marketplace EQP API uses a two-step process to authenticate a client application and authorize access to resources:
- Using the API access key, obtain a session token.
- Create the API access key from one, or both, of the Marketplace Developer Portal user interfaces:
- production - https://commercedeveloper.adobe.com
- sandbox - https://commercedeveloper-sandbox.adobe.com
- From the Marketplace Developer Portal, sign in, click on the account name (top, right corner), and choose either the Account Information or the Marketplace Profile link.
- From the left-hand side navigation menu, click on Manage API Keys.
- Click Create API Access Key.
- In the "Create New API Key" dialog, enter an API Key Name. This name is for internal reference only. Then, click Continue.
- The API access key consists of two values, an Application ID and an Application Secret. Enter both into the connection configuration, along with the Use Production Environment toggle set to match the portal (production or sandbox) used to create the key.
Configure the Connection
- Application ID: the application ID generated by the Marketplace Developer Portal when the API access key is created.
- Application Secret: the application secret generated alongside the Application ID.
- Use Production Environment: a boolean toggle. Set to
trueto use the production environment (https://commercedeveloper-api.adobe.com); set tofalseto use the sandbox environment (https://commercedeveloper-sandbox-api.adobe.com). Defaults tofalse(sandbox).
| Input | Comments | Default |
|---|---|---|
| Application ID | The application ID half of a Marketplace API access key. Generate one in the Marketplace Developer Portal under your account name > Account Information > Manage API Keys. See API access keys. | |
| Application Secret | The application secret issued alongside the application ID above, from the same Marketplace API access key. The key can be regenerated or deleted at any time under Manage API Keys. See API access keys. | |
| Use Production Environment | Set true for production environment (https://commercedeveloper-api.adobe.com), false for sandbox (https://commercedeveloper-sandbox-api.adobe.com). | false |
OAuth 1.0a
Authenticate with an Adobe Commerce store using an integration's OAuth 1.0a credentials.
OAuth 1.0a authenticates requests against a merchant's own Adobe Commerce store, and is the authentication method to use for reading and writing store data such as orders, products, customers and transactions.
An integration activated in the Adobe Commerce Admin issues four credentials: a consumer key, a consumer secret, an access token and an access token secret. There is no login screen and no token to request: the four values sign every request directly, and neither secret is ever transmitted to the store.
Prerequisites
- A merchant-hosted Adobe Commerce store reachable over HTTPS. A store reachable only over plain HTTP is not supported.
- An administrator account with permission to create integrations
Adobe Commerce as a Cloud Service authenticates through Adobe's Identity Management System instead and is not supported by this connection. Refer to Authentication in Adobe Commerce as a Cloud Service.
Setup Steps
To create an integration and obtain its credentials:
- Log in to the Adobe Commerce Admin.
- Navigate to System > Extensions > Integrations.
- Click Add New Integration and enter a Name.
- Open the API tab and grant the resource access the integration requires. Reading orders, products and customers requires at least Sales, Catalog and Customers.
- Click Save.
- Click Activate on the new integration, review the requested access, and click Allow.
- Copy all four values from the Integration Tokens for Extensions dialog.
The four values are shown only at activation, so they must be copied before the dialog is closed. Lost credentials are replaced by reauthorizing the integration, which issues a new set. The credentials do not expire. They stay valid until the integration is deactivated or reauthorized.
Refer to Integrations for more information on creating and activating an integration, and to Authentication for Adobe's description of the OAuth 1.0a method.
Configure the Connection
Create a connection of type OAuth 1.0a and configure the following fields:
- Enter the store's base URL into Store URL, without a trailing slash and without the
/restpath (for example,https://www.example.com). - Enter the four values copied at activation into Consumer Key, Consumer Secret, Access Token and Access Token Secret.
- Optionally set Store Code. It defaults to
default, the store view code a single-store installation ships with, and forms the<store_code>segment of the/rest/<store_code>/V1request path. Change it only on a store that serves multiple store views.
| Input | Comments | Default |
|---|---|---|
| Store URL | The base URL of the Adobe Commerce store, without a trailing slash and without the /rest path. | |
| Consumer Key | The consumer key shown when an integration is activated under System > Extensions > Integrations in the Adobe Commerce Admin. See Authentication. | |
| Consumer Secret | The consumer secret issued alongside the consumer key above. It is used to sign each request and is never sent to the store. | |
| Access Token | The access token issued when the integration was activated. Unlike a bearer token it is not sufficient on its own: it identifies the integration, and the access token secret below proves possession. | |
| Access Token Secret | The access token secret issued alongside the access token above. It is used to sign each request and is never sent to the store. | |
| Store Code | The store view code requests are scoped to, used as the <store_code> segment of /rest/<store_code>/V1. Leave as default unless the store serves multiple store views. | default |
Triggers
New and Updated Records
Checks a Magento resource collection (orders, customers, or products) on a configured schedule for records whose updated_at is at or after the last poll. Records whose created_at is also after the last poll are included in the payload's body.data.created array; older records modified since the last poll are included in body.data.updated.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Resource Type | The Magento resource collection to poll for new and updated records. | orders |
| Look-back Date | The date the initial sync starts from, in YYYY-MM-DD format. Cannot be a future date. Leave empty to start from the first recurrence with no backfill. When set, the initial sync seeds each record modified on or after this date once, ignoring the field and visibility filters. | |
| Show New Records | When true, records whose created_at falls after the last poll are included in the payload's body.data.created array. | true |
| Show Updated Records | When true, records whose updated_at falls after the last poll but were created earlier are included in the payload's body.data.updated array. | true |
Webhook
Receive webhook requests from Adobe Commerce for webhooks you configure.
Actions
Cancel Order
Cancels a specified order.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Order ID | The order to act on, identified by its Magento entity_id rather than the customer-facing increment ID. Pick an order from the dropdown or supply the ID directly. |
Create Customer
Create customer account.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Customer | The customer record to save, as a JSON object under a customer key. The default value lists every field the endpoint accepts; remove the ones that do not apply. | |
| Password | The password to set on the new customer account. When provided it is added to the request body as password; leave it blank to omit it from the request. | |
| Redirect URL | The URL sent alongside the new customer account as redirectUrl, used as the destination of the account confirmation link. Leave it blank to omit it from the request. |
Create Order
Performs persist operations for a specified order.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Order | The order to create, as a JSON object under an entity key. The default value lists every field the endpoint accepts; remove the ones that do not apply. | |
Create Product Attributes
Save attribute data
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Product Attribute | The product attribute to save, as a JSON object under an attribute key. The default value lists every field the endpoint accepts; remove the ones that do not apply. | |
Create Product Options
Save Custom Option
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Product Option | The custom product option to save, as a JSON object under an option key. The option is tied to a product through its product_sku field. The default value lists every field the endpoint accepts. | |
Create Products
Create a new Product
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Product | The product to save, as a JSON object under a product key. The default value lists every field the endpoint accepts; remove the ones that do not apply. | |
Delete Customer
Delete customer by Customer ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Customer ID | The customer to act on, identified by their Magento customer id. Pick a customer from the dropdown or supply the ID directly. |
Get Customer
Get customer by Customer ID.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Customer ID | The customer to act on, identified by their Magento customer id. Pick a customer from the dropdown or supply the ID directly. |
Get Order
Loads a specified order.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Order ID | The order to act on, identified by its Magento entity_id rather than the customer-facing increment ID. Pick an order from the dropdown or supply the ID directly. |
Get Transaction
Loads a specified transaction.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Transaction ID | The payment transaction to retrieve, identified by its Magento transaction_id rather than the payment gateway's own txn_id. Pick a transaction from the dropdown or supply the ID directly. |
List Order Items
Lists order items that match specified search criteria.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
List Orders
Lists orders that match specified search criteria.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
List Product Attributes
Retrieve product attributes that match specified search criteria.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
List Product Option Types
Get custom option types
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. |
List Products
Get product list
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
List Product Types
Retrieve available product types
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. |
List Transactions
Lists transactions that match specified search criteria.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
Raw Request (GraphQL)
Send a raw GraphQL request to Adobe Commerce.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Store | The hostname of the storefront that receives the GraphQL request. The request is sent to https://<host>/graphql, so this must be a bare host with no scheme and no path. | |
| GraphQL Query | The GraphQL operation to send to the store's /graphql endpoint. The default value is a placeholder outline; replace it with the query or mutation to run. | query myCartQuery{ cart(cart_id: String!): Cart } |
Raw Request (REST)
Send a raw HTTP request to Adobe Commerce.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| URL | Input the path only. The base URL comes from the connection: the Store URL for the OAuth 1.0a connection, or the Marketplace sandbox or production host for the API Access Key connection. The path is appended to that base as-is, so a store REST path includes its /rest/<store_code>/V1 prefix, where <store_code> is whatever the OAuth 1.0a connection's Store Code field holds (for example, /rest/default/V1/orders for the default store view). | |
| Method | The HTTP method to use. | |
| Data | The HTTP body payload to send to the URL. | |
| Form Data | The Form Data to be sent as a multipart form upload. | |
| File Data | File Data to be sent as a multipart form upload. | |
| File Data File Names | File names to apply to the file data inputs. Keys must match the file data keys above. | |
| Query Parameter | A list of query parameters to send with the request. This is the portion at the end of the URL similar to ?key1=value1&key2=value2. | |
| Header | A list of headers to send with the request. | |
| Response Type | The type of data you expect in the response. You can request json, text, or binary data. | json |
| Timeout | The maximum time that a client will await a response to its request | |
| Retry Delay (ms) | The delay in milliseconds between retries. This is used when 'Use Exponential Backoff' is disabled. | 0 |
| Retry On All Errors | If true, retries on all erroneous responses regardless of type. This is helpful when retrying after HTTP 429 or other 3xx or 4xx errors. Otherwise, only retries on HTTP 5xx and network errors. | false |
| Max Retry Count | The maximum number of retries to attempt. Specify 0 for no retries. | 0 |
| Use Exponential Backoff | Specifies whether to use a pre-defined exponential backoff strategy for retries. When enabled, 'Retry Delay (ms)' is ignored. | false |
Search Customers
Retrieve customers which match a specified criteria.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Fetch All | When true, walks the result set page by page and returns every record instead of a single page. Page Size still controls how many records each page requests (100 when left blank), while Current Page is ignored because paging always restarts at page 1. Paging stops after 100 pages. | false |
| Current Page | The page of results to return, counting from 1. Ignored when Fetch All is enabled, which always starts at page 1. | |
| Page Size | How many records to return per page. When Fetch All is enabled and this is left blank, each page requests 100 records. | |
| Condition Type | The Magento condition type used to compare Field against Value, such as an equality or range operator. Omit it to let Magento apply its own default comparison. | |
| Field | The record field the search filter is applied to. Only one filter is supported: Field, Condition Type and Value together build searchCriteria[filterGroups][0][filters][0], so a single request can filter on one field only. | |
| Value | The value that Field is compared against. It belongs to the same single filter as Field and Condition Type, so only one value can be matched per request. Dates use the Magento YYYY-MM-DD HH:MM:SS UTC format rather than ISO 8601. | |
| Sorting Direction | The direction the Sorting Field is ordered in. It has no effect unless Sorting Field is also set. | |
| Sorting Field | The record field that results are sorted by. Pair it with Sorting Direction to control the order. |
Update Customer
Update an existing customer.
| Input | Comments | Default |
|---|---|---|
| Connection | The Adobe Commerce connection to use. | |
| Customer ID | The customer to act on, identified by their Magento customer id. Pick a customer from the dropdown or supply the ID directly. | |
| Customer | The customer record to save, as a JSON object under a customer key. The default value lists every field the endpoint accepts; remove the ones that do not apply. | |
| Password Hash | An already-hashed password to store on the customer, for migrating an account whose credentials were created elsewhere. When provided it is added to the request body as passwordHash; leave it blank to omit it from the request. |