Access control for Experience Platform is administered through the Adobe Admin Console. This functionality leverages product profiles in Admin Console, which link users with permissions and sandboxes. See the access control overview for more information.
This developer guide provides information on how to format your requests to the Access Control API, and covers the following operations:
The following sections provide additional information that you will need to know in order to successfully make calls to the Schema Registry API.
This guide 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.
In order to make calls to Platform APIs, you must first complete the authentication tutorial. Completing the authentication tutorial provides the values for each of the required headers in all Experience Platform API calls, as shown below:
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 the operation will take place in:
For more information on sandboxes in Platform, see the sandbox overview documentation.
All requests that contain a payload (POST, PUT, PATCH) require an additional header:
Now that you have gathered the required credentials, you can now continue to read the rest of the developer guide. Each section provides important information regarding their endpoints and demonstrate example API calls for performing CRUD operations. Each call includes the general API format, a sample request showing required headers and properly formatted payloads, and a sample response for a successful call.