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 client-to-server and server-to-server API calls.

Authenticated API calls enable use cases that allow for secure collection of sensitive data according to your organization's privacy policies. In addition to authentication, the Edge Network API supports marking datastreams to accept only authenticated communication.

The Media Edge API currently supports client-to-server API calls only.

Authenticated API calls use server.adobedc.net endpoints.
Non-authenticated API calls use edge.adobedc.net endpoints.

Maintaining consistent edge routing

The Edge Network uses globally distributed servers and DNS-based routing to handle each request from the location closest to the end user. If a session crosses regions (such as if a user connects to a VPN or switches between mobile networks), subsequent requests can land on a different server. Mid-session routing changes can fragment user profile processing, since Adobe Experience Platform and Adobe Experience Cloud solutions store profile state on the server that initially handled the session.

Every Edge Network response includes a location hint value (such as or2 or va6) that identifies the server that processed the request. To keep traffic on the same edge location for the remainder of the session, insert that value into the URL path of subsequent requests, between the base path and the API version:

POST https://edge.adobedc.net/ee/{LOCATION_HINT}/v2/interact?datastreamId={DATASTREAM_ID}

All endpoints described in this guide support this routing pattern. See Location hints for the full list of valid values, the recommended cookie format for persisting the hint across requests, and the equivalent format for authenticated endpoints.