(Alpha) HTTP Destination


The HTTP destination in Platform is currently in alpha. The documentation and the functionality are subject to change.


The HTTP destination is an Adobe Experience Platform streaming destination that helps you send profile data to third-party HTTP endpoints.

To send profile data to HTTP endpoints, you must first connect to the destination in Adobe Experience Platform.

Use Cases

The HTTP destination is targeted towards customers who need to export XDM profile data and audience segments to generic HTTP endpoints.

HTTP endpoints can be either customers’ own systems or third-party solutions.

Connect to Destination

In Connections > Destinations, select HTTP API, and select Configure.

Activate HTTP Destination


If a connection with this destination already exists, you can see an Activate button on the destination card. For more information about the difference between Activate and Configure, refer to the Catalog section of the destination workspace documentation.

Activate HTTP Destination

In the Account step, you need to define the HTTP endpoint connection details. Select New account and enter the connection details for the HTTP endpoint that you want to connect to.

  • httpEndpoint: the complete URL of the HTTP endpoint that you want to send the profile data to.
    • Optionally you can add query parameters to the httpEndpoint URL.
  • authEndpoint: the complete URL of the HTTP endpoint used for OAuth2 authentication.
  • Client ID: the clientID parameter used in the OAuth2 client credentials.
  • Client Secret: the clientSecret parameter used in the OAuth2 client credentials.

Only OAuth2 client credentials are currently supported.

HTTP endpoint connection

Click Connect to destination. After the connection succeeds, click Next.

In the Authentication step, enter the account authentication credentials:

  • Name: enter a name by which you will recognize this destination in the future.
  • Description: enter a description that will help you identify this destination in the future.
  • Custom Headers: enter any custom headers that you want to be included in the destination calls, following this format: header1:value1,header2:value2,...headerN:valueN.

The current implementation requires at least one custom header. This limitation will be resolved in a future update.

HTTP authentication

Marketing use case: Marketing use cases indicate the intent for which data will be exported to the destination. You can select from Adobe-defined marketing use cases or you can create your own marketing use case. For more information about marketing use cases, see the Data usage policies overview.

Click Create destination.

Activate Segments

See Activate profiles and segments to a destination for information about the segment activation workflow.

Destination Attributes

During the Select attributes step, when activating segments to an HTTP destination, we recommend that you select a unique identifier from your union schema. Select the unique identifier and any other XDM fields that you want to export to the destination.

Exported data

Your exported Experience Platform data lands in your HTTP destination in JSON format. For example, the event below contains the email address profile attribute of an audience that has qualified for a certain segment and exited another segment. The identities for this prospect are ECID and email.

  "person": {
    "email": "yourstruly@adobe.con"
  "segmentMembership": {
    "ups": {
      "7841ba61-23c1-4bb3-a495-00d3g5fe1e93": {
        "lastQualificationTime": "2020-05-25T21:24:39Z",
        "status": "exited"
      "59bd2fkd-3c48-4b18-bf56-4f5c5e6967ae": {
        "lastQualificationTime": "2020-05-25T23:37:33Z",
        "status": "existing"
  "identityMap": {
    "ecid": [
        "id": "14575006536349286404619648085736425115"
        "id": "66478888669296734530114754794777368480"
    "email_lc_sha256": [
        "id": "655332b5fa2aea4498bf7a290cff017cb4"
        "id": "66baf76ef9de8b42df8903f00e0e3dc0b7"

On this page