APIs for builders
Adobe CX Enterprise APIs give developers and AI-assisted coding agentic tools direct access to Adobe data and workflows. Use them to build custom applications, automate integrations, and embed Adobe capabilities into your own systems. APIs are the right choice when you need full programmatic control over a system integration or are building an application on top of Adobe data. For agent-driven, conversational access to Adobe workflows, see MCP servers.
Adobe CX Enterprise APIs
Reporting, data feeds, calculated metrics, and segment management.
REST and GraphQL APIs for catalog, cart, orders, customers, and promotions.
CRUD operations for datasets, schemas, profiles, identities, queries, and segmentation.
Journey orchestration, campaign management, content templates, and offer decisioning.
Content, asset, and workflow management APIs for Adobe Experience Manager.
Audience management and activation workflows.
Mobile SDKs, edge SDKs, and in-app messaging.
Analytics data access, reporting, and CJA insights workflows.
Edge Network data ingestion, real-time event collection, and streaming data delivery.
API project setup, authentication, and credential management.
Event-driven integrations, webhooks, and automation triggers.
Privacy workflows, data governance, and data subject requests.
User management, identity administration, and enterprise account automation.
Build with APIs
Coding agents like Claude Code, Cursor, and OpenAI Codex are well-suited for building with Adobe CX Enterprise APIs. Add an OpenAPI spec to your project and the agent can discover endpoints, construct requests, and reason about API behavior without manual wiring. To start, you need two things: authenticated credentials from Adobe Developer Console, and API documentation added to your project.
Set up API credentials in Adobe Developer Console
All Adobe CX Enterprise API access is managed through Adobe Developer Console. Create a project, add the APIs your application needs, and generate credentials.
- Sign in and create a project in Adobe Developer Console.
- Add the API for the Adobe CX Enterprise application you need.
- Choose an authentication type. Use OAuth Server-to-Server for automated workflows or OAuth Web App for user-facing applications.
- Generate your credentials. Note the client ID, client secret, and token endpoint for use in your application.
Most Adobe CX Enterprise APIs require application licensing. If an API is not available in your Developer Console project, contact your Adobe representative.
Add Adobe API context to your project
AI coding agents can reliably discover and use Adobe APIs when you add the right reference material to your project. This works for any Adobe CX Enterprise API that publishes an OpenAPI specification.
1. Find the API specification
Browse the Adobe CX Enterprise APIs listed above or go directly to the Adobe Developer API catalog.
2. Download the OpenAPI spec
Create a /specs directory in your project. Download the OpenAPI YAML from the API references page on developer.adobe.com and save it there. Add a README.md recording the source URL and download date.
/specs/README.md
/specs/aem-assets.openapi.yaml
3. Generate an API index
Paste this prompt into your coding agent, replacing <API-SPEC-FILE> with your filename:
Read /specs/<API-SPEC-FILE>.openapi.yaml and generate /docs/<API-SPEC-FILE>.api.md.
Create a concise API index for AI coding agents. For each operation include: operationId, HTTP method, path, purpose, authentication requirements, required inputs, response shape, common error responses, pagination behavior, asynchronous behavior, and deprecation status.
Do not invent endpoints, parameters, request bodies, response fields, or behavior not present in the OpenAPI specification.
4. Generate agent instructions
Read /specs/<API-SPEC-FILE>.openapi.yaml and /docs/<API-SPEC-FILE>.api.md.
Generate AGENTS.md. Instructions should:
- Treat the OpenAPI specification as the source of truth.
- Use the API index as a navigation guide.
- Never invent endpoints, parameters, response fields, or status codes.
- Prefer documented operationIds.
- Avoid deprecated or experimental APIs unless explicitly requested.
- Follow authentication requirements defined in the specification.
- Use the local OpenAPI snapshot for implementation decisions.
5. Verify
Ask your coding agent to complete a simple task using only the generated files:
Write a function that takes an AEM asset ID and returns the asset title and description. Use only /specs/aem-assets.openapi.yaml and /docs/aem-assets.api.md.
If the agent completes it correctly without inventing behavior, setup is complete.
Recommended project structure
project/
├── specs/
│ ├── README.md
│ └── aem-assets.openapi.yaml
├── docs/
│ └── aem-assets.api.md
└── AGENTS.md
Keeping specs current
When Adobe publishes a new API version: download a fresh snapshot into /specs, update the date in README.md, and regenerate the index and AGENTS.md.
APIs in action
APIs give development teams full programmatic control to build focused applications that automate specific CX Enterprise workflows. These walkthroughs show real integrations built end to end, from credential setup to working code your organization can ship.
Invoke AEM APIs from a web app
Build a web application that authenticates users and calls AEM OpenAPIs using OAuth to deliver governed, programmatic access.