Adobe Journey Optimizer APIs Authentication

Adobe Journey Optimizer API access is set up through the steps below. Each of these steps is detailed in the Adobe Developer documentation.

JWT Deprecation Notice

The JWT method to generate access tokens has been deprecated. All new integrations must be created using the OAuth Server-to-Server authentication method. Adobe also recommends that you migrate your existing integrations to the OAuth method. Read the following important documentation:

• Migration guide for your applications from JWT to OAuth
• Implementation guide for new and old applications with OAuth
• Advantages of using the OAuth Server-to-Server credentials method

To manage certificates in Adobe Developer, make sure you have System administrator rights on the organization or a developer account in the Admin Console.

Prerequisites

Create a new integration to Adobe Journey Optimizer Service in Adobe Developer Console and configure it. Your credentials will then be generated (API Key, Client secret...).

1. Create a new project.
2. Add the AJO API.
   
3. Add AEP Permissions to the role that coincides with the product profile you included for the AJO API.
   

Authorization header

To establish a secure service-to-service Adobe Developer API session, every request to an Adobe service must include in the Authorization header the information below.

Copy
-X GET https://cjm.adobe.io/imp/ \
-H 'Content-Type: application/json' \
-H 'Cache-Control: no-cache' \
-H 'Authorization: Bearer <ACCESS_TOKEN>' \
-H 'X-Api-Key: <API_KEY>' \
-H 'x-gw-ims-org-id: <IMS_ORG>'
Copied to your clipboard
-X GET https://cjm.adobe.io/imp/ \
-H 'Content-Type: application/json' \
-H 'Cache-Control: no-cache' \
-H 'Authorization: Bearer <ACCESS_TOKEN>' \
-H 'X-Api-Key: <API_KEY>' \
-H 'x-gw-ims-org-id: <IMS_ORG>'

• IMS_ORG: 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 Developer when creating a new integration, in the licenses list.

• ACCESS_TOKEN: Generate an access token in the Adobe Developer Console after creating a new integration to Adobe Journey Optimizer Service.

• API_KEY: The client id generated by in Adobe Developer Console after creating a new integration to Adobe Journey Optimizer Service.

Permissions

Ensure that the product profile associated with the API integration has the required permissions for the API you want to call. Also ensure that the AEP role associated with the product profile has been give permissions in the AEP Permissions UI.

An administrator can create the product profile in Adobe Admin Console and can also associate the API integration to the product profile.

Depending on the API, different permissions need to be configured:

• Capping API needs the "Manage Journeys Events, Data Sources and Action" permission to the targeted sandbox (Capping is configured at sandbox level).
• Throttling API needs the "Manage Journeys Events, Data Sources and Action" permission to the production sandbox (Throttling can only be configured on the production sandbox)
• Journey API needs the "Journey Manage" and "Journey View" permissions to the targeted sandbox.
  
  

Last updated 10/1/2025

Was this helpful?

Yes

No