🔐 1. Adobe I/O Console – The One Entry Point
Purpose: Central hub for creating projects, generating credentials (JWT or OAuth2), and enabling services.
Tip: You must register every project here before using any other Adobe API.
🧱 2. Experience Platform API – Your Foundation Layer
Purpose: Manage core Experience Platform components like:
‣ XDM schemas
‣ Datasets
‣ Batch ingestions
‣ Data views (for CJA)
Use cases:
- Automatically create a new XDM schema
- Upload a CSV file into a dataset
- Check batch ingestion status
⚡ 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
🧠 4. Segmentation Service API – Audience Engine
Purpose: Programmatically manage Adobe segments:
‣ Create new segments
‣ Refresh them
‣ Fetch profiles matching a segment
Use cases:
- Trigger segment recalculation via API
- Schedule dynamic audience updates
- Export eligible profiles to a destination
🔍 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
🎯 6. Real-Time CDP API – 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
📊 7. Adobe Analytics API (v2.0) – Workspace Insights
Purpose: Extract Workspace data via API:
‣ Metrics
‣ Dimensions
‣ Segments
‣ Saved reports
Use cases:
- Get top 10 most viewed pages
- Export daily KPIs to Slack or email
- Build dashboards outside of Workspace
🧪 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
✉️ 9. Adobe Campaign Standard API – Messaging Control
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
🛠️ 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://<host>/collection/yourDatasetId \
-H “Authorization: Bearer <your_access_token>” \
-H “x-api-key: <your_client_id>” \
-H “x-gw-ims-org-id: <your_org_id>” \
-H “Content-Type: application/json” \
-d ‘{
“eventType”: “productPurchase”,
“timestamp”: “2025-08-05T10:10:00Z”,
“product”: “Coffee Mug”,
“price”: 12.99
}
🧠 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.
Leave a Reply