# POST /ims/exchange/jwt stops working

Calls to POST /ims/exchange/jwt* on Adobe IMS stopped working on June 30, 2025.

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.

## What to use instead

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.

- API: Adobe IMS (ims-na1.adobelogin.com)
- Kind: Endpoint removal
- Announced: May 1, 2023
- Takes effect: June 30, 2025
- Calls after that day: fail
- Calls it hits: `POST /ims/exchange/jwt*`
- Source: [Announcement](https://developer.adobe.com/developer-console/docs/guides/authentication/ServerToServerAuthentication/migration)
- Verified: October 26, 2026, against Adobe IMS's own pages
- Page: https://www.okapi.bot/providers/adobe-ims/breaking-changes/post-ims-exchange-jwt-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent