- Platform Tutorials
- Introduction to Platform
- A customer experience powered by Experience Platform
- Behind the scenes: A customer experience powered by Experience Platform
- Experience Platform overview
- Key capabilities
- Application and Intelligent Services
- Integrations with Experience Cloud applications
- Key use cases
- Basic architecture
- Using the Platform user interface
- Roles and project phases
- Getting started: Data Architects and Data Engineers
- Authenticate to Experience Platform APIs
- Import sample data to Experience Platform
- Administration
- Audit logs
- Data Collection
- Data Governance
- Data Hygiene
- Data Ingestion
- Overview
- Batch ingestion overview
- Create and populate a dataset
- Map a CSV file to XDM
- Sources overview
- Ingest data from Adobe Analytics
- Ingest data from Audience Manager
- Ingest data from cloud storage
- Ingest data from CRM
- Ingest data from databases
- Streaming ingestion overview
- Stream data with HTTP API
- Stream data using Source Connectors
- Web SDK tutorials
- Mobile SDK tutorials
- Data Science Workspace
- Overview
- Architecture
- Load data in JupyterLab notebooks
- Query and discover data in JupyterLab notebooks
- Exploratory Data Analysis
- Recipes, models, and services overview
- Build a model using the recipe builder template
- Analyze model performance
- Create and publish a trained model (UI)
- Schedule automated training and scoring for a service
- Enrich Real-time Customer Profiles with machine learning insights
- Package source files into a recipe
- Import a packaged recipe (UI)
- Import a packaged recipe (API)
- Destinations
- Destinations overview
- Connecting to destinations
- Create destinations and activate data
- Activate profiles and segments to a destination
- Integrate with Google Customer Match
- Configure the Azure Blob destination
- Configure the Marketo destination
- Configure file-based cloud storage or email marketing destinations
- Configure a social destination
- Next-hit personalization with Adobe Target
- Activate data to non-Adobe applications webinar
- Identities
- Monitoring
- Profiles
- Privacy
- Introduction to Privacy Service
- Identity data in Privacy requests
- Privacy JavaScript library
- Privacy labels in Adobe Analytics
- Getting started with the Privacy Service API
- Privacy Service UI
- Privacy Service API
- Subscribe to Privacy Events
- 10 considerations for Responsible Customer Data Management
- Elevating the Marketer’s Role as a Data Steward
- Queries
- Schemas
- Segments
- Segment Builder Overview
- Create segments
- Create content-based segments
- Create conversion segments
- Create segments from existing segments
- Create sequential segments
- Create dynamic segments
- Create multi-entity segments
- Create segments with B2B data
- Demo of streaming segmentation
- Evaluate a segment
- Create a dataset to export data
- Segment Match connection setup
- Segment Match data governance
- Segment Match configuration flow
- Segment Match pre-share insights
- Segment Match receiving data
- Sources
- Application Services
- Intelligent Services
- Experience Cloud Integrations
- Industry Trends
Authenticate and access Experience Platform APIs
In order to make calls to Adobe Experience Platform APIs, you must first gain access to an Experience Platform developer account.
For step-by-step instructions outlining how to gain access to a developer account, please visit the Experience Platform API authentication tutorial.
Create and export Experience Platform API to Postman
Postman is a tool allowing developers to quickly and easily interact with Adobe Experience Platform APIs.
Adobe Developer Console’s Export Details for Postman capability provides an easy way to export all the account details required to access and interact with an Experience Platform API in a single Postman Environment file, removing the need to copy and paste values from Adobe Developer Console into Postman.
Generate an Access Token with Postman
Use the Adobe Identity Management Service APIs to obtain an Access Token to access the Adobe Experience Platform APIs for Non-production Use
As noted in the Adobe I/O Access Token Generation Postman collection, the denoted generation methods are suitable for non-production use. Local Signing loads a JavaScript library from a 3rd-party host, and Remote signing sends the private key to an Adobe owned and operated web service. While Adobe does not store this private key, production keys should never be shared with anyone.
Interacting with Adobe I/O APIs using Postman
Explore interacting with Adobe I/O APIs using the Adobe-provided Experience Platform API Postman collections, building upon the Adobe I/O Environment Variables and generated access token.
Note that Adobe-provided Postman collections may not exist for every Adobe I/O API, however the provided Experience Platform API Postman collections can be used as a guide on how to define your own Postman collections for these use-cases.
Additional Resources
Business.Adobe.com resources
Resources
Adobe Account
