API Overview
The DA REST API — create, read, update, and delete content programmatically.
Document Authoring exposes a small family of HTTP APIs, Source, Config, Version, Move, Copy, and List, that together cover the full lifecycle of content stored in DA. They all share one host and one authentication model, so once you understand the common pattern, every individual API is a small variation on it.
Base URL
All admin APIs are served from:
https://admin.da.livePaths are namespaced by API family, then by organization and repository, e.g. /source/{org}/{repo}/{path} or /list/{org}/{repo}/{path}.
Authentication
Every request must carry a valid Adobe IMS access token as a bearer token:
Authorization: Bearer {IMS_TOKEN}Requests without a valid token receive an empty 401 response. Some operations additionally check DA's permissions configuration for the target org/repo.
Common patterns
- Reads (
GET) return the raw resource, HTML, JSON, an image, or a listing, with a200, or an empty404if nothing exists at that path. - Writes (
POST) that create or replace a resource send amultipart/form-databody (adatafield for the Source API, aconfigfield for the Config API, adestinationfield for Move/Copy) and return201on creation or204on a no-content success such as a move or copy. - Deletes (
DELETE) are idempotent and return an empty204. - Folder paths (no file extension) are treated differently from file paths (with an extension) across several of these APIs, see each API's page for the specifics.
The APIs
- Source — create, read, and delete folders, HTML documents, JSON sheets, and media.
- Config — read and write project-level configuration for an org/repo.
- Version — snapshot, list, and retrieve historical versions of a document.
- Move — relocate or rename a file.
- Copy — duplicate a file to a new path.
- List — enumerate the contents of a folder.
Read the full API overview at docs.da.live/developers/api.