Adobe Campaign Standard API access is set up through the steps below. Each of these steps is detailed in the Adobe Developer documentation.
To manage certificates in Adobe Developer, make sure you have System administrator rights on the organization or a developer account in the Admin Console.
To establish a secure service-to-service Adobe I/O API session, every request to an Adobe service must include in the Authorization header the information below.
-X GET https://mc.adobe.io/<ORGANIZATION>/campaign/profileAndServices/profile \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <ACCESS_TOKEN>' \
-H 'Cache-Control: no-cache' \
-H 'X-Api-Key: <API_KEY>'
<ORGANIZATION>: This is your personal ORGANIZATION ID, one ORGANIZATION ID is provided by Adobe for each of your instances :
To obtain your ORGANIZATION ID value, refer to your administrator or your Adobe technical contact. You can also retrieve it into Adobe I/O when creating a new integration, in the licenses list (see the Adobe Developer documentation).
<ACCESS_TOKEN>: Your personal access token, that was retrieved when exchanging your JSON Web Token through a POST request.
<API_KEY>: your personal API Key. It is provided in Adobe I/O after creating a new integration to Adobe Campaign Service.
During AdobeIO integration, if the following error appears:
{
"code": 502,
"message": "Oops. Something went wrong. Check your URI and try again."
}
Refer to your administrator or your Adobe technical contact to check if the CNAME parameter is created correctly.