Show Menu
SUJETS×

Getting started with the Real-time Customer Profile API

Using the Real-time Customer Profile API, you can perform basic CRUD operations against Profile resources, such as configuring computed attributes, accessing entities, exporting Profile data, and deleting unneeded datasets or batches.
Using the developer guide requires a working understanding of the various Adobe Experience Platform services involved in working with Profile data. Before beginning to work with the Real-time Customer Profile API, please review the documentation for the following services:
The following sections provide additional information that you will need to know in order to successfully make calls to Profile API endpoints.

Lecture d’exemples d’appels API

The Real-time Customer Profile API documentation provides example API calls to demonstrate how to properly format requests. Il s’agit notamment de chemins d’accès, d’en-têtes requis et de payloads de requêtes correctement formatés. L’exemple JSON renvoyé dans les réponses de l’API est également fourni. 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.

En-têtes requis

La documentation de l’API exige aussi que vous ayez suivi le tutoriel sur l’authentification pour lancer des appels vers des points de terminaison Platform 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: {IMS_ORG}
All resources in Experience Platform are isolated to specific virtual sandboxes. Requests to Platform APIs require a header that specifies the name of the sandbox the operation will take place in:
  • x-sandbox-name: {SANDBOX_NAME}
For more information on sandboxes in Platform, see the sandbox overview documentation .
Toutes les requêtes ayant un payload dans le corps de la requête (notamment les appels POST, PUT et PATCH) doivent comporter un en-tête Content-Type . Les valeurs acceptées propres à chaque appel sont fournies dans les paramètres d’appel.

Étapes suivantes

Pour commencer à lancer des appels à l’aide de l’ Real-time Customer Profile API, sélectionnez l’un des guides de points de terminaison disponibles.