adobe.com
Adobe exposes HTTP APIs including AEM OpenAPI-based APIs, Adobe Experience Platform APIs, and Adobe Commerce REST APIs; recorded auth uses Adobe Developer Console OAuth bearer tokens for AEM, bearer token + `x-api-key` + `x-gw-ims-org-id` for Experience Platform, and Commerce REST auth remains undetermined from the recorded docs.
- Adobe Experience Manager OpenAPI APIsdiscovered
- Adobe Experience Platform APIsdiscovered
- Adobe Commerce REST APIsdiscovered
Create a project in Adobe Developer Console and add the relevant API or service. For AEM OpenAPI-based APIs, Adobe documents OAuth Server-to-Server, OAuth Web App, and OAuth Single Page App credentials configured through Console projects in the OpenAPI-Based APIs overview. Use the Console-generated credentials to obtain a bearer token for API calls.
Create a project in Adobe Developer Console and add the target Adobe API. Adobe Experience Platform and related APIs require the project's client ID as the x-api-key header; Adobe also refers to this as the API key in pages such as the Data Access API reference.
Use the Adobe organization associated with your Adobe Developer Console project. Experience Platform API docs state requests require the organization ID in the x-gw-ims-org-id header, and note it can be copied from your Experience Platform interface or project context on pages like the Data Access API reference.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://adobe.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing