Hi @MitchellTe1 ,
You're absolutely right to follow the Adobe Experience League Postman + Adobe Analytics API guide, but the issue you're facing with multiple companies during OAuth token generation is a known and frustrating limitation in some cases.
Use Adobe Developer Console JWT Integration Instead
This is the most stable method for multi-org setups.
Steps:
-
Go to Adobe Developer Console
-
Create a new JWT credential project for Adobe Analytics API
-
Choose the correct Organization (Org ID) when creating the integration
-
Download the private key + JSON config
-
Use Postman or a script to exchange for a token with this payload.
Adobe Docs: JWT Authentication
Use the Right Org in Postman Header After Token Is Generated
Even if you manage to get a token via OAuth flow, you must pass the correct company ID (IMS Org ID) in the header of every request:
x-proxy-global-company-id: your_company_id
To find this:
Run the OAuth flow in Incognito browser and pre-select org
Sometimes Adobe gets confused with stored sessions. Try:
-
Run OAuth callback URL in Incognito browser
-
Select your org → Adobe redirects back → manually copy the code from URL
-
Paste the code into Postman → exchange for access token
Alternative: Use Service Account (JWT) or API key-based auth
If this is system-to-system access, the JWT auth method (client credentials) is more stable.
Avoid using OAuth flows with multi-org users for backend/API tasks unless you're doing user-level scoped tasks.