Configure authentication for Adobe Target APIs

In the Adobe Admin Console, ensure your Adobe user account has been granted both Product Admin and Developer level access to Target.

In the Adobe Developer Console, select the Experience Cloud Organization for which you want to create this integration. (Note it is likely you may only have access to a single Experience Cloud Organization.)

Click Create new project.

Click Add API to add a REST API to your project to access Adobe services and products.

Select Adobe Target as the Adobe service you wish to integrate with. Click the Next button that appears.

Select an option for associating public and private keys with the service account integration you are creating for Target. For this example, select Option 1: Generate a key pair and click Generate keypair.

As instructed, make note of the automatically downloaded configuration file (config), which contains your private key. Click Next.

In your file system, verify the location of config, which is the compressed configuration file created in the previous step. Again, this config file contains your private key, which you will need later. The exact location within your file system may differ from the one shown here.

Back in the Adobe Developer Console, select the product profile(s) corresponding to the properties in which you are using Adobe Recommendations. (If you are not using properties, select the Default Workspace option.) Click Save configured API.

Click Create Integration. You should receive a temporary message indicating your API was successfully configured.

As a final step, rename your project to a name more meaningful than the original Project 1. To do this, navigate to the project using the navigation path as show, click Edit project to access the Edit Project modal, and rename the project.

Still in the Adobe Developer Console, navigate to view your new project’s Service Account (JWT) credentials. Use either the left navigation or the Credentials section as shown.

In Credential details, note you may view your Public key(s), Client ID, and other information related to your service account.

Click to navigate to information about the Adobe Target API. Use either the left navigation or the Connected products and services section as shown.

Click Download for Postman > Service Account (JWT) to create a JSON file capturing your authentication information for a Postman environment.

Note the JSON file in your file system.

In Postman, click the gear icon to manage your environments, then click Import to import the JSON file (environment).

Choose your file and click Open.

In the Postman Manage Environments modal, click the name of the newly imported environment to inspect it. (Your environment name may be different from the one shown here. Edit the name as desired. It does not necessarily need to match the name of the Adobe project.)

Note CLIENT_SECRET and API_KEY (along with other variables) have their values pre-populated, taken from your integration as defined in the Adobe Developer Console. (The Postman CLIENT_SECRET variable should match the CLIENT SECRET Adobe credential as displayed in the Developer Console, and API_KEY in Postman should likewise match CLIENT ID in the Developer Console.) By contrast, note PRIVATE_KEY, JWT_TOKEN, and ACCESS_TOKEN are blank. Let’s start by providing the PRIVATE_KEY value.

From your file system, open your config file, and open the private key file.

Select and copy the entire contents of the private key file.

In Postman, paste your private key value into the INITIAL VALUE and CURRENT VALUE fields.

Click Update, and close the Environments modal.

Navigate to the Adobe Identity Management Service API sample calls.

Click the Adobe I/O Access Token Generation Postman collection.

Get the raw JSON for this collection by clicking Raw, then copying the resulting JSON to your clipboard. (Alternatively, you can save the raw JSON as a .json file.)

In Postman, import the collection by pasting and submitting the raw JSON from your clipboard. (Alternatively, you can upload the .json file you saved.) Click Continue.

Select the IMS: JWT Generate + Auth via User Token request in the Adobe I/O Access Token Generation Postman collection, ensure your environment is selected, and click Send to generate the token.

Open the Manage Environments modal again, and select your environment.

Note the ACCESS_TOKEN and JWT_TOKEN values are now populated.

Import the Adobe Target Admin APIs Postman Collection. Follow all prompts until the collection is imported in Postman.

Expand the collection, and note the List activities request.

Note that variables such as {{access_token}} are initially unresolved. You could resolve this in several different ways—for example, you could define a new collection variable called {{access_token}}—but in this guide, you will instead change the API request to leverage the Postman environment you were previously using. This will enable the environment to continue to serve as a single, consistent consolidation of all variables common across Adobe APIs.

Type to replace {{access_token}} with {{ACCESS_TOKEN}}.

Type to replace {{api_key}} with {{API_KEY}}.

Type to replace {{tenant}} with {{TENANT_ID}}. Note {{TENANT_ID}} is not yet recognized.

Open the Manage Environments modal, and select your environment.

Type to add a new {{TENANT_ID}} environment variable. Copy and paste your Tenant ID value into the INITIAL VALUE and CURRENT VALUE fields for your new TENANT_ID environment variable.

Send your request, after ensuring you have selected the correct environment. You should receive a response containing your list of activities.