Files
6 files · 974 KB · verbatim copies of public vendor files| File | Format | Size | Download |
|---|---|---|---|
aem_openapi_assets-author_experimental-metaall_2026.07.yaml | OpenAPI | 236 KB | Download |
aem_openapi_assets-author_stable_2026.07.yaml | OpenAPI | 144 KB | Download |
aem_openapi_assets-delivery-dm_experimental-advancemodifiers_2026.07.yaml | OpenAPI | 226 KB | Download |
aem_openapi_assets-delivery-dm_stable_2026.07.yaml | OpenAPI | 255 KB | Download |
aem_openapi_folders_stable_2026.07.yaml | OpenAPI | 52 KB | Download |
aem_openapi_tags-author_experimental-tags_2026.07.yaml | OpenAPI | 60 KB | Download |
README — provenance
DAM Wiki downloaded these files on 2026-09-30 from public vendor URLs; all files re-checked against the registry on 2026-10-13 (one file updated, one added — see the table). The API reference pages on developer.adobe.com render these OpenAPI documents with Redoc; each page declares its source in a data-src attribute pointing to Adobe's Redocly registry. They are unmodified copies, exactly as the vendor serves them. DAM Wiki refreshes these copies when the AEM release notes (https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/release-notes/release-notes/release-notes-current) or the spec info.version changes (current: 2026.07). Adobe can change a spec's content without bumping info.version (observed 2026-10-13 on the Dynamic Media with OpenAPI stable spec), so compare bytes, not only the version.
Download pattern: https://api.redocly.com/registry/bundle/adobe-developers/{API}/{channel}/openapi.yaml (a .json variant is also served).
Notes
serversin every spec ishttps://{bucket}.adobeaemcloud.com/…where{bucket}isauthor-p{program}-e{env}(author tier) ordelivery-p{program}-e{env}(Dynamic Media with OpenAPI delivery tier).- Security schemes: HTTP bearer (IMS access token) and
X-Api-Keyheader (Developer Console client ID); delivery endpoints for approved, unrestricted assets allow anonymous access (security: [{}]). - Events are declared under the non-standard top-level key
x-webhooks(OpenAPI 3.0 has nowebhooks), payloads in CloudEvents format. - Not stored: Content AI APIs (
AEM-contentAI/stableand/aemcontentai, AI/generative search over AEM content sources — https://api.redocly.com/registry/bundle/adobe-developers/AEM-contentAI/stable/openapi.yaml?branch=prod), and non-Assets AEM APIs (Sites, Forms, Translation, etc.) listed on https://developer.adobe.com/experience-cloud/experience-manager-apis/. - Not covered by any spec (prose only on Experience League): legacy Assets HTTP API (
/api/assets), direct binary upload (.initiateUpload.json/.completeUpload.json), Query Builder (/bin/querybuilder.json). - No official Postman collection was found.
- Quick inventory:
python -c "import yaml;s=yaml.safe_load(open('aem_openapi_assets-author_stable_2026.07.yaml',encoding='utf-8'));print([(m.upper(),p) for p,o in s['paths'].items() for m in o if m in ('get','post','put','patch','delete','head')])" - Release 28871 (AEM as a Cloud Service maintenance release, notes updated 2026-10-10) announces new Assets OpenAPI capabilities (collections update/delete/search, async copy, metadata export, task search, download jobs, named-rendition deletion). As of 2026-10-13 none of them appears in the published Assets Author or Folders specs, which are byte-identical to the 2026-09-30 copies; only tag management is covered, by the Tag Author API above.