POST /ims/exchange/jwt* → endpoint removal
Adobe IMS
Stopped working
On June 30, 2025, POST /ims/exchange/jwt* stops working as Service Account (JWT) credentials reach their end of life and are no longer supported. Calls to this endpoint will fail after that date.
Calls it hits
POST /ims/exchange/jwt*
What to use instead of these calls
Add an OAuth Server-to-Server credential to your project in the Adobe Developer Console. Request tokens using POST /ims/token/v3 with grant_type=client_credentials, client_id, client_secret, and scope instead of exchanging a signed JWT.
In Adobe IMS's words
As of June 30, 2025, Service Account (JWT) credentials have reached their end of life and are no longer supported. All server-to-server integrations must use the OAuth Server-to-Server credentials.
Facts
- API
- Adobe IMS
ims-na1.adobelogin.com - Kind
- Endpoint removal
- Announced
- May 1, 2023
- Takes effect
- June 30, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Adobe IMS's own pages
Questions
When does this change take effect?
Calls to POST /ims/exchange/jwt* on Adobe IMS stopped working on June 30, 2025.
What happens to calls after June 30, 2025?
They have failed since June 30, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.