15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform
15+Years Trading
£3bnRevenue Processed
75Team Size
B2C & B2BExperience
Strategy-ledRetainer
1 WeekDiscovery
< 6 MonthsReplatform

Single GraphQL API for Commerce SaaS Services

Adobe announces unified GraphQL endpoint for Product Recommendations, Live Search, and Catalog Service, simplifying merchant integrations.

4 min
Single GraphQL API for Commerce SaaS Services

On January 22, 2024, Adobe unveiled a significant architectural improvement: a unified GraphQL API endpoint for all Commerce SaaS services. Previously, merchants had to manage separate endpoints for Product Recommendations, Live Search, and Catalog Service. This consolidation simplifies integration logic and reduces the operational complexity of managing multiple API connections.

The Challenge of Multiple Endpoints

Modern composable storefronts often rely on multiple Adobe services: Catalog Service for product data, Live Search for search and filtering, and Product Recommendations for personalisation. Each service previously required its own endpoint, authentication, rate limiting, and error handling. This fragmentation created integration challenges and increased the cognitive load on development teams.

The Unified Approach

Adobe's new unified endpoint allows merchants to query all three services through a single GraphQL gateway. Developers can now construct queries that combine product data, search results, and recommendations in one call, reducing API overhead and simplifying client-side logic. This architectural simplification benefits both development velocity and application performance.

Implementation Benefits

With a single endpoint, merchants achieve cleaner code, reduced network overhead, simpler error handling, and centralised monitoring and analytics. Development teams can focus on building features rather than managing complex API orchestration logic.

Backward Compatibility

Adobe maintained full backward compatibility, allowing merchants to migrate to the unified endpoint at their own pace. Legacy integrations using individual endpoints continue to function without modification, providing a smooth transition path for existing implementations.

Strategic Implications

This move reinforces Adobe's commitment to composable, developer-friendly commerce. By removing integration friction, Adobe makes it easier for merchants to adopt its SaaS services and build modern, performant storefronts. For merchants evaluating platform strategies, simplified integrations reduce time-to-market and lower long-term maintenance costs.

Want to read more insights?

View All Articles