DocumentationTutorialsUse Cases & Blueprints

Environment file

Last update: September 11, 2026

CREATED FOR:

  • Developer
  • User

Postman environment file

Download File — AEP Bootcamp.postman_environment.json

Import environment file

  1. Open the Environment File from above in your browser by clicking on the file
  2. Copy the URL of the file to your clipboard
  3. Launch Postman on your local machine and click on the Import button within your workspace
  4. Paste the URL of the Environment File into the import modal text box on the overlay. This should trigger an automatic import

Clicking the Import button in the Postman workspace to import the environment file

Pasting the environment file URL into the Postman import modal text box

Once imported, you can validate your environment file exists by clicking on the Environments tab in the left sidebar. You should see something similar to below.

AEP Bootcamp environment listed under the Postman Environments tab after import

Environment variables

Before you can make any API calls you need to update a few of the variables in the environment file you just imported. These variables are referenced in the API calls so be sure they are correctly filled in. The variables are broken into two groups:

  • Developer Project Values -> these are the default variables generated from the Developer Project that were created in the Adobe Developer Console
  • Other Values -> these are custom created variables that are typically created by a user to work with the various Experience Platform APIs
NOTE
These values come from the OAuth Server-to-Server credential you created in Developer Console Setup

Update developer project values

  1. Click on the Environments tab in the left sidebar of Postman

  2. Next click on the AEP Bootcamp environment file

  3. Update the current values for the below listed variables:

    • CLIENT_SECRET
    • CLIENT_ID (also called API KEY)
    • TECHNICAL_ACCOUNT_ID
    • IMS_ORG

When done your environment file should look similar to this:

Environment file after updating CLIENTSECRET, CLIENTID, TECHNICALACCOUNTID, and IMSORG values

Update other values

The only other values that need to be updated are the SANDBOX_NAME variable and the TENANT_NAME variable.

  • SANDBOX_NAME - tells Adobe Experience Platform what sandbox to execute against
  • TENANT_NAME - used to pre-populate the tenant name in specific XDM calls
NOTE
If you’re working through these labs at your own pace (rather than a live training event with a sandbox-assignment.pdf), you can find both values while logged into your sandbox from the Adobe Experience Platform UI URL, for example:
https://experience.adobe.com/#/@dep/sname:prod/platform/home
  • SANDBOX_NAME is the value after sname: — in this example, prod
  • TENANT_NAME is the value after the @ symbol, prefixed with an underscore — in this example, _dep

  1. Update the current values for the below listed variables:

    • SANDBOX_NAME
    • TENANT_NAME

  2. Save your updates by clicking the Save button in the top right of the environment workspace

When you are done your environment file should look like this:

Environment file after updating the SANDBOXNAME and TENANTNAME values

TIP
Congratulations! You have completed your Postman Environment configuration
recommendation-more-help
blueprints-learn-help-blueprints