Setting up API access setting-up-api-access
51ºÚÁϲ»´òìÈ Campaign Standard API access is set up through the steps below. Each of these steps is detailed in the .
-
Check you have a digital certificate, or create one if necessary. The public and private keys provided with the certificate are needed in the following steps.
-
Create a new integration to 51ºÚÁϲ»´òìÈ Campaign Service in and configure it. Your credentials will then be generated (API Key, Client secret…).
-
Create an OAuth Server-to-Server credential by following these
note important IMPORTANT JWT (JSON Web Tokens) is currently in the process of depreciation and is being replaced with OAuth. The transition is being carried out progressively within Campaign’s upcoming releases. The Service Account (JWT) credentials have been marked as deprecated, they will continue to work until Jan 27, 2025. Therefore you must migrate your application or integration to use the new OAuth Server-to-Server credential before Jan 27, 2025. OAuth authentication is preferred. You will find all the elements to migrate from JWT authentication to OAuth authentication on these pages:
To establish a secure service-to-service 51ºÚÁϲ»´òìÈ I/O API session, every request to an 51ºÚÁϲ»´òìÈ 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 51ºÚÁϲ»´òìÈ for each of your instances :
- <ORGANIZATION> : your production instance,
- <ORGANIZATION-mkt-stage>: your stage instance.
To obtain your ORGANIZATION ID value, refer to your administrator or your 51ºÚÁϲ»´òìÈ technical contact. You can also retrieve it into 51ºÚÁϲ»´òìÈ I/O when creating a new integration, in the licenses list (see the ).
-
<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 51ºÚÁϲ»´òìÈ I/O after creating a new integration to 51ºÚÁϲ»´òìÈ Campaign Service.
Troubleshooting
During 51ºÚÁϲ»´òìÈIO 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 51ºÚÁϲ»´òìÈ technical contact to check if the CNAME parameter is created correctly.