APIs

API family
Primary purpose
Used by
Commerce Foundation GraphQL APIs
Core commerce and transactional capabilities such as catalog operations, cart, checkout, customers, and orders
Adobe Commerce on Cloud, Adobe Commerce on premises, and Adobe Commerce as a Cloud Service
Storefront Services GraphQL APIs
Storefront-oriented catalog, search, and recommendation experiences through Catalog Service, Live Search, and Product Recommendations
Adobe Commerce on Cloud or on premises with configured services, and Adobe Commerce as a Cloud Service
Commerce Optimizer Merchandising Services GraphQL APIs
Retrieve Optimizer-managed catalog, catalog views, price contexts, search, recommendations, and merchandising results
Adobe Commerce on Cloud or on premises with the Optimizer Connector, and stand-alone Adobe Commerce Optimizer
Commerce Optimizer Data Ingestion REST API
Add catalog and price data to a stand-alone Adobe Commerce Optimizer implementation
Stand-alone Adobe Commerce Optimizer connected to an external data source

Commerce Foundation GraphQL APIs

Core commerce capabilities including catalog, cart, checkout, customers, and orders. Used by Adobe Commerce on Cloud, Adobe Commerce on premises, and Adobe Commerce as a Cloud Service. See the Commerce GraphQL API.

Storefront Services GraphQL APIs

Storefront-oriented catalog, search, and recommendation experiences through Catalog Service, Live Search, and Product Recommendations. Used by Adobe Commerce on Cloud, on-premises, and Adobe Commerce as a Cloud Service. See the Storefront Services GraphQL schema.

Commerce Optimizer Merchandising Services GraphQL APIs

Retrieve Optimizer-managed catalog, catalog views, price contexts, search, recommendations, and merchandising results. Used by Adobe Commerce on Cloud, on-premises with the Adobe Commerce Optimizer Connector, and stand-alone Adobe Commerce Optimizer. See Commerce Optimizer Merchandising Services.

Commerce Optimizer Data Ingestion REST APIs

Add catalog and price data to a stand-alone Adobe Commerce Optimizer implementation from an external data source. See Commerce Optimizer Data Ingestion.

Commerce Optimizer integrations

Adobe Commerce Optimizer connects to other systems through several integration paths, depending on whether it is paired with Adobe Commerce or a third-party backend.

Adobe Commerce Optimizer Connector

Synchronizes catalog and price data from Adobe Commerce on Cloud or on-premises to Adobe Commerce Optimizer, keeping Adobe Commerce as the transaction system while Optimizer provides discovery and merchandising. See Commerce Optimizer Integrations.

Third-party commerce integrations

Ingests catalog and price data from a third-party commerce platform, PIM, ERP, or other source into stand-alone Adobe Commerce Optimizer through the Data Ingestion REST API, while the third-party platform remains the transactional system of record.

API Mesh and App Builder

Use API Mesh to orchestrate Adobe Commerce APIs with private or third-party APIs. Use Adobe Developer App Builder to build custom applications and integrations. For related Commerce extensibility guidance, see API Mesh and Adobe Commerce extensibility.

For event-driven integrations specifically, see Adobe I/O Events for Adobe Commerce.

Cart and checkout handoff

For stand-alone Adobe Commerce Optimizer with an external backend, the storefront uses Merchandising Services GraphQL APIs for product experiences, then hands off cart, checkout, customer, order, payment, tax, shipping, and fulfillment to the backend via API Mesh, App Builder, or direct integration.

AEM Assets

AEM Assets is an optional, cross-cutting digital asset management integration that can be added to any Commerce or Optimizer architecture rather than a separate integration path of its own. See AEM Assets integration for Commerce.

recommendation-more-help
commerce-help-information-center