Adobe Commerce REST

Adobe Commerce (formerly Magento 2) is an enterprise e-commerce platform. This connector uses the REST API.

Overview

The Adobe Commerce REST connector hits the admin REST API of Adobe Commerce (formerly Magento 2). It is the back-office counterpart to the GraphQL storefront connector: products, categories, orders, customers, invoices, shipments, and store config are all exposed as first-class operations.

Use it as the source-of-truth side of a multi-channel setup (pushing orders into NetSuite, syncing products to other channels), as the destination for migrations from other platforms, or as the admin layer behind an AI shopping assistant that needs to create invoices or shipments programmatically.

What You Can Do

The Adobe Commerce REST connector exposes these tools:

  • list-products - List products with filters (SKU, status, type, attribute set).
  • get-product - Fetch a single product with its full attribute set.
  • create-product / update-product / delete-product - Full product CRUD.
  • check-product-salability - Check whether a product is currently salable.
  • get-source-items - Read per-source inventory rows for multi-source merchants.
  • get-category-tree - Fetch the full category tree.
  • create-category / update-category / delete-category - Category CRUD.
  • list-orders - List orders with filters (status, date, customer).
  • get-order - Fetch a single order with line items and addresses.
  • create-invoice - Create an invoice against an existing order.
  • create-shipment - Create a shipment against an existing order.
  • list-customers / get-customer / create-customer - Customer reads and create.
  • list-coupons - List sales rule coupons.
  • get-store-config - Read store config (base URLs, currency, locale).
  • raw-rest-request - Call any Adobe Commerce REST endpoint that does not have a dedicated tool.

Authentication

The Adobe Commerce REST API uses bearer tokens minted via the Integrations interface. In Adobe Commerce admin go to System -> Integrations -> Add New Integration, grant the API resources your workflows need (typically Catalog, Sales, and Customers), save, then click Activate and copy the access token.

You also need the REST endpoint URL for your store, typically https://your-store.com/rest/V1 or /rest/all/V1. The connector uses the bearer token in the Authorization header on every call.

Setting Up Your Connection

  1. In Adobe Commerce admin, open System -> Integrations -> Add New Integration, grant the resources you need, save and activate, then copy the access token.
  2. Confirm your REST base URL (usually https://your-store.com/rest/V1).
  3. In Spojit, go to Connections and click + Add Connection.
  4. Search for Adobe Commerce REST and select it.
  5. Paste the base URL and access token. Name the connection something descriptive (e.g. Adobe Commerce - Production Admin).
  6. Click Save. Spojit calls get-store-config to verify the credentials.

Using in a Workflow

Add a Connector node, select your Adobe Commerce REST connection, and pick a mode:

  • Direct Mode - Use for deterministic syncs like "list orders since yesterday, create invoices and shipments." The tool sequence is fixed and inputs come from the trigger.
  • Agent Mode - Use for ad-hoc admin tasks where an AI agent investigates and acts ("find recent orders from this customer and refund the most expensive one").

For endpoints not covered by a dedicated tool (e.g. credit memos, shopping cart price rules), use raw-rest-request rather than building extra connectivity.

Tips

  • Batch with raw-rest-request. The async bulk API can apply hundreds of updates in a single call - much faster than per-row CRUD.
  • Filter on updated_at for incremental syncs. list-orders and list-products both accept search criteria; filter by updated_at > last-run to avoid full table scans.
  • Set a high pageSize for reads. Default page sizes are small; bumping to 100-250 cuts round-trips for large catalogs.
  • Use multi-source inventory tools deliberately. If your store uses multi-source, get-source-items is the source of truth - the legacy stock fields on products lag.
  • Re-issue invoices and shipments idempotently. Always check get-order for existing invoices before calling create-invoice.

Common Pitfalls

  • Integration scope mismatch. If you forget to grant a resource on the integration, calls fail with a 401 even though the token is valid - go back to the integration and re-grant.
  • Store view vs default scope. Many endpoints behave differently against /V1/ vs /all/V1/ - confirm which scope you actually want, especially for multi-store merchants.
  • Tax-inclusive prices. Stores in AU, UK, and EU return prices inclusive of tax. Convert before syncing to systems that expect pre-tax totals (NetSuite, Stripe).
  • Attribute set drift. create-product validates against the product's attribute set; cloning attributes across sets without aligning them is a common source of 400s.
  • Test in a sandbox. delete-product and delete-category have no undo - always test against a non-production store first.

Common Use Cases

Related Articles

For technical API details and field specifications, see the Adobe Commerce REST connector documentation.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.