Getting started with the Unified Tags API

The Unified Tags API lets you categorize and manage your business objects within Adobe Experience Platform.

The following sections provide additional information that you will need to know in order to successfully work with the Unified Tags API.

Reading sample API calls

The Unified Tags API documentation provides example API calls to demonstrate how to format your requests. These include paths, required headers, and properly formatted request payloads. Sample JSON returned in API responses is also provided. For information on the conventions used in documentation for sample API calls, see the section on how to read example API calls in the Experience Platform troubleshooting guide.

Required headers

The API documentation also requires you to have completed the authentication tutorial in order to successfully make calls to Platform endpoints. Completing the authentication tutorial provides the values for each of the required headers in Experience Platform API calls, as shown below:

• Authorization: Bearer {ACCESS_TOKEN}
• x-api-key: {API_KEY}
• x-gw-ims-org-id: {ORG_ID}

All resources in Experience Platform are isolated to specific virtual sandboxes. All requests to Platform APIs require a header that specifies the name of the sandbox in which the operation will take place:

• x-sandbox-name: {SANDBOX_NAME}

Next steps

To being making calls using the Unified Tags API, select one of the available endpoint guides either using the left navigation or within the developer guide overview