Data collection API endpoints

The Adobe Experience Platform Edge Network provides an optimized way for you to send data to any Adobe Experience Cloud product or Adobe Experience Platform service.

You can use these API endpoints for various data collection, personalization, advertising and marketing use cases. Since they do not rely on any libraries to load, they provide a lightning-fast way to interact with the Edge Network and supported solutions.

data-slots=video

https://video.tv.adobe.com/v/341448/

Adobe offers several endpoints that facilitate the interaction with the Edge Network, through the APIs below:

Edge Network API: Includes the interact and collect endpoints, sending data directly to a datastream
Media Edge API: Includes 18 endpoints that allow you to compose a streaming media session on Adobe's servers. When the session completes, those events are aggregated into a smaller number of events and sent to the desired datastream.

The benefits of using these endpoints include:

Reduced page load time
Improved latency
First-party data collection
Streamlined, server-side communication between services

data-variant=warning

data-slots=text

These endpoints are subject to additive changes and their behavior can evolve without notice. For example, Adobe may add new objects or properties to response payloads in the future.

Make sure that any implementations using these APIs can accommodate additional fields without failing. Any breaking changes, such as the removal of request or response objects, are released as a new incremental API version.

Authenticated data collection

The Edge Network API supports both authenticated and non-authenticated API calls, for server-to-server and client-to-server data collection. The Media Edge API currently supports client-to-server API calls only. See Authentication to learn when to use each type of call, which hostname each one uses, and how to authenticate your requests.

Maintaining consistent edge routing

The Edge Network returns a location hint that identifies the edge server that processed a request. To keep user profile processing consistent, include this location hint in the URL path of subsequent requests in the same session. All endpoints described in this guide support this routing pattern. See Location hints for the URL format, the list of valid values, and how to persist the hint across requests.