Also known as meshConfig
The JSON file that defines a mesh. The limit is 375 KB, or 750 KB when content is moved into a files array (raised in September 2026).
Last checked 2026-09-30
CX Enterprise atlas / Developer & Extensibility | Developer & extensibility
API Mesh for Adobe Developer App Builder
ProductGenerally available
Developer & ExtensibilityDeveloper & extensibility
Also known as API Mesh for App Builder, API Mesh, Adobe API Mesh
A hosted API orchestration layer, based on GraphQL Mesh, that combines GraphQL, REST (OpenAPI) and JSON sources into one GraphQL endpoint. Developers configure a mesh in JSON with sources, transforms, resolvers, hooks and caching, deploy it to an App Builder workspace with the aio CLI, and serve it from Adobe's edge network. Adobe Commerce is its main use.
Built on 1
Integrates with 5
- Adobe Developer Console
- API orchestration with API Mesh
- Third-party cart and checkout
- Adobe Commerce
- Adobe Commerce Optimizer
Integrated by 3
- Adobe Developer App Builder: API Mesh template
- Adobe Developer Console
- Adobe Commerce: Commerce boilerplate
Contains 6 parts, 44 entries
- Mesh configuration# Collection
- Source handlers# Collection
Handlers bring an API into the mesh. Each source gets one handler, and schemas are cached until the mesh is updated.
Last checked 2026-09-30
- GraphQL handler# Capability
Connects a GraphQL endpoint by introspection or from a schema file; since May 2026 a local .graphql file can be referenced directly in the source field.
Last checked 2026-09-30
- OpenAPI handler# Capability
Turns a REST API described by an OpenAPI or Swagger document into GraphQL types and operations.
Last checked 2026-09-30
- JSON Schema handler# Capability
Connects REST endpoints without an OpenAPI document by describing requests and responses with JSON schemas or samples.
Last checked 2026-09-30
- Prebuilt mesh sources# Capability
Also known as api-mesh-sources
Ready-made source configurations for first- and third-party APIs, kept in the api-mesh-sources repository and installed with aio api-mesh source commands; third parties add sources by pull request.
Last checked 2026-09-30
- Transforms# Collection
Ordered changes to the schema, applied to one source or the whole mesh, that control what requests and responses contain.
Last checked 2026-09-30
- Prefix transform# Capability
Adds a prefix to a source's types and root fields, for example to avoid name conflicts between the Commerce API and Catalog Service.
Last checked 2026-09-30
- Filter Schema transform# Capability
Removes types, fields or arguments from the exposed schema.
Last checked 2026-09-30
- Type Merging transform# Capability
Combines partial definitions of one type from several sources into a single type.
Last checked 2026-09-30
- Naming Convention transform# Capability
Applies a consistent case style to type, field and enum names.
Last checked 2026-09-30
- Encapsulate transform# Capability, limited availability
Wraps a source's schema under a single field, for example to combine two Commerce GraphQL endpoints. Accepted by API Mesh but not fully supported.
Last checked 2026-09-30
- Federation transform# Capability, limited availability
Adds the resolvers and directives needed to conform to the Apollo Federation specification. Accepted but not fully supported.
Last checked 2026-09-30
- Replace Field transform# Capability, deprecated
Replaced one field with another. Deprecated and not available in edge meshes; custom resolvers cover the same need.
Replaced by Programmatic resolvers
Last checked 2026-09-30
- Custom resolvers# Collection
Also known as additionalResolvers
Ways to extend the combined schema with new types and fields and define how they resolve across sources.
Last checked 2026-09-30
- Additional type definitions# Capability
Also known as additionalTypeDefs
Adds types or fields to the unified schema, inline or, since March 2026, from .graphql files.
Last checked 2026-09-30
- Declarative resolvers# Capability
Configuration-only resolvers that fill a new field by calling an operation on another source.
Last checked 2026-09-30
- Programmatic resolvers# Capability
JavaScript resolver files uploaded with the mesh, for logic such as applying third-party discounts to Commerce product prices.
Last checked 2026-09-30
- Batching# Capability
Resolvers that combine repeated lookups into one request to sources that support it, avoiding the n+1 problem and rate limits.
Last checked 2026-09-30
- Mesh hooks# Capability
Local or remote functions (for example App Builder actions) run before or after operations, blocking or not, for tasks such as checking authentication. They cannot change the request or response.
Last checked 2026-09-30
- Context state# Capability
Globally distributed key-value storage available to hooks and resolvers at the edge, typically for reusing authentication tokens across requests.
Last checked 2026-09-30
- Mesh secrets# Capability
A separate YAML file of up to 50 secrets (5 KB each) referenced from the mesh configuration; values cannot be read back after deployment.
Last checked 2026-09-30
- Headers and CORS# Capability
Operation headers sent to sources, response headers and CORS rules set in the mesh configuration.
Last checked 2026-09-30
- Edge meshes# Service
API Mesh runs on an edge network in about 330 locations at edge-graph.adobe.io. Legacy (non-edge) mesh endpoints were switched off on 3 December 2024.
Last checked 2026-09-30
- Native caching# Capability
Response caching built into API Mesh, controlled by cache-control headers from the sources or the mesh, and purged with aio api-mesh cache purge.
Last checked 2026-09-30
- Fastly caching# Integration
Use of the customer's Fastly CDN in front of a mesh, with Commerce VCL snippets and a header that stops Fastly caching requests coming from the mesh.
Last checked 2026-09-30
- Legacy mesh endpoints# Capability, deprecated
The original, non-edge mesh hosting, disabled on 3 December 2024.
Replaced by Edge meshes
Last checked 2026-09-30
- API Mesh security# Collection
Always-on protections plus settings that owners control. API Mesh adds no authentication of its own; it passes source authorization headers through to the back ends.
Last checked 2026-09-30
- WAF, DDoS protection and rate limiting# Capability
Global protections that cannot be switched off: a web application firewall, DDoS mitigation, rate limiting and a 60-second timeout on every request.
Last checked 2026-09-30
- Query hardening# Capability
Also known as queryConfig
Optional limits added in June 2026 against oversized or probing queries: query cost, depth, aliases, directives and tokens, suppressed field suggestions and masked resolver errors.
Last checked 2026-09-30
- Introspection control# Capability
Lets owners turn off GraphQL introspection, which Adobe recommends for production meshes.
Last checked 2026-09-30
- API Mesh developer tools# Collection
The CLI plugin, Console views and project tooling for creating, testing and deploying meshes.
Last checked 2026-09-30
- API Mesh CLI plugin# API / SDK
Also known as aio-cli-plugin-api-mesh, aio api-mesh
The aio api-mesh commands: init and run for local work; create, update, status, get, describe and delete for a workspace's mesh; source commands; log-list, log-get and log-get-bulk; cache purge; and config for log forwarding.
Integrates with: I/O CLI
Last checked 2026-09-30
- Mesh local development# Capability
aio api-mesh init creates a local project (optionally a Git repo) and aio api-mesh run serves the mesh locally with environment variables, local files and secrets.
Last checked 2026-09-30
- API Mesh in Developer Console# Capability
The workspace's API Mesh page shows the active configuration, a GraphiQL playground and the deployment history with status and error logs.
Integrates with: Developer Console
Last checked 2026-09-30
- API Mesh starter kit# Capability
Also known as api-mesh-starter-kit
A GitHub template repository that creates and deploys a mesh with GitHub Actions and holds AI prompting resources (an llm.txt knowledge file and Cursor rules). A December 2025 guide covers generating mesh configurations with AI coding agents.
Last checked 2026-09-30
- Mesh CI/CD and performance testing# Capability
Guidance for deploying meshes from pipelines with I/O Management API credentials, and k6 performance tests run locally or on a schedule in GitHub.
Last checked 2026-09-30
- API Mesh logging# Capability
Request logs for edge meshes, looked up by ray ID or exported for a 30-minute window from the last 30 days.
Last checked 2026-09-30
- New Relic log forwarding for API Mesh# Integration
Forwards mesh logs to New Relic, currently the only supported destination.
Last checked 2026-09-30
- API Mesh for Adobe Commerce# Collection
The Commerce patterns documented for API Mesh: combining Commerce GraphQL and REST, Catalog Service and Live Search with other APIs, and connecting storefronts to back-end systems.
Integrates with: API orchestration with API Mesh
Last checked 2026-09-30
- Storefront integration# Integration
A low-code way to bring other APIs to the Commerce storefront and the Storefront Management APIs; the Edge Delivery Services Commerce boilerplate can point at a mesh endpoint.
Integrates with: Commerce Storefront
Last checked 2026-09-30
- Third-party cart and checkout with API Mesh# Integration
Commerce Optimizer storefronts call an external commerce platform's cart and checkout through API Mesh and App Builder.
Integrates with: Third-party cart and checkout
Last checked 2026-09-30