Adobe APIs Explained: What Each One Does

🔐 1. Adobe Developer Console – The One Entry Point

Purpose: Central hub for creating projects, generating credentials (OAuth Server-to-Server for back-end jobs; JWT credentials reached end of life on June 30, 2025, see Adobe: migration from JWT), and enabling services.
Tip: almost every Adobe API needs a Developer Console project and credentials (exception: unauthenticated streaming connections).

👉 Documentation

🧱 2. Experience Platform API – Your Foundation Layer

Purpose: Manage core Experience Platform components like:
‣ XDM schemas
‣ Datasets
‣ Batch ingestions

Use cases:

Automatically create a new XDM schema
Upload a CSV file into a dataset
Check batch ingestion status

👉 Documentation

⚡ 3. Streaming Ingestion API – Real-Time Data In

Purpose: Send real-time events from backends, CRMs, apps, etc.
Use cases:

Push a purchase event from your backend
Connect offline systems to Adobe
Track non-web customer interactions

👉 Documentation

🧠 4. Segmentation Service API – Audience Engine

Purpose: Programmatically manage Adobe segments:
‣ Create segment definitions (audiences)
‣ Run segment jobs to evaluate them
‣ Run export jobs to extract qualified profiles

Use cases:

Trigger segment recalculation via API
Schedule dynamic audience updates
Export eligible profiles to a destination

👉 Documentation

🔍 5. Query Service API – SQL for XDM

Purpose: Query Adobe datasets using SQL, optionally saving results to a dataset.
Use cases:

Explore data using SQL
Automate advanced analytics without UI
Create post-processing pipelines

👉 Documentation

🎯 6. Destinations & Flow Service APIs (Real-Time CDP) – Activate to Destinations

Purpose: Control audience activations to various destinations:
‣ Paid media (Facebook, Google)
‣ Internal tools or CRMs
‣ Data lakes

Use cases:

Trigger Facebook audience sync
List available destinations
Automate activation jobs

👉 Documentation · Flow Service API

📊 7. Adobe Analytics API (v2.0) – Workspace Insights

Purpose: Extract Workspace data via API:
‣ Metrics
‣ Dimensions
‣ Segments
‣ Calculated metrics and other components

Use cases:

Get top 10 most viewed pages
Export daily KPIs to Slack or email
Build dashboards outside of Workspace

👉 Documentation

📈 7 bis. Customer Journey Analytics API – Connections, Data Views, Reports

Purpose: Manage Customer Journey Analytics components:
‣ Connections
‣ Data views
‣ Reports

👉 Documentation

🧪 8. Adobe Target API – Experiment Automation

Purpose: Manage A/B and multivariate testing:
‣ Create or modify activities
‣ Retrieve test results
‣ Adjust targeting rules

Use cases:

Launch experiments via API
Monitor performance
Update content dynamically

👉 Documentation

✉️ 9. Adobe Campaign Standard API – Messaging Control
(Campaign Standard customers are being moved to Campaign v8 — check which product you have before building on this API. See Adobe Campaign Standard documentation.)

Purpose: Manage email/SMS/push delivery from Campaign:
‣ Create or update user profiles
‣ Add users to lists
‣ Trigger transactional messages

Use cases:

Trigger emails from a webhook
Sync data between systems
Control Campaign workflows from external apps

👉 Documentation

🛠️ Bonus APIs You Should Know

‣ Schema Registry API – define and version schemas
‣ Catalog Service API – browse datasets and metadata
‣ Access Control API – manage user rights and permissions

⚙️ Sample Call — Streaming Ingestion API

curl -X POST 'https://dcs.adobedc.net/collection/{CONNECTION_ID}?syncValidation=true' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer {ACCESS_TOKEN}' \
  -H 'x-api-key: {API_KEY}' \
  -H 'x-gw-ims-org-id: {ORG_ID}' \
  -d '{
  "header": {
    "datasetId": "{DATASET_ID}",
    "flowId": "{FLOW_ID}",
    "imsOrgID": "{ORG_ID}"
  },
  "body": {
    "xdmMeta": {
      "schemaRef": {
        "id": "https://ns.adobe.com/{TENANT_ID}/schemas/{SCHEMA_ID}",
        "contentType": "application/vnd.adobe.xed-full+json;version=1"
      }
    },
    "xdmEntity": {
      "_id": "...",
      "timestamp": "2025-08-05T10:10:00Z",
      "eventType": "commerce.purchases"
    }
  }
}'

The ID in the URL is the streaming connection ID, not a dataset ID. The body is XDM: a header (dataset, flow, org) and a body with the schema reference and the event. A flat JSON body only works if a dataflow with data prep mapping is set up. The authorization headers are only needed for authenticated connections. Source: Adobe: stream time-series data.

🧠 Final Thoughts
Adobe’s ecosystem is modular — and so are its APIs. Each API targets a specific part of the data lifecycle:

‣ Data ingestion (batch + real-time)
‣ Audience creation and segmentation
‣ Data exploration via SQL
‣ Cross-channel activation
‣ Analytics extraction
‣ Message delivery

Knowing which API to use (and how to authenticate properly) unlocks powerful automation and customization possibilities across your stack.

Full Guide: What Adobe APIs Are Available and What They Do

Related reading