/v1/* → version retirement
Circle CCTP API
Deprecated, no date
Deprecation of /v1/* begins on October 31, 2026, and completes on December 1, 2026, when these endpoints fail in favor of CCTP V2. All calls to /v1/* are affected across iris-api.circle.com.
Calls it hits
/v1/*
What to use instead of these calls
Use the CCTP V2 API by calling GET /v2/messages/{sourceDomainId}?transactionHash={hash} for messages and attestations, along with GET /v2/publicKeys. The transition requires more than updating endpoints, as CCTP V2 uses new contracts at new addresses, new ABIs, and a Fast Transfer fee.
CCTP V2 uses new contracts at new addresses, new ABIs and a Fast Transfer fee: the onchain integration moves too, not only the API calls.
In Circle CCTP API's words
CCTP V1 (Legacy) deprecation begins October 31, 2026 and completes on December 1, 2026, in favor of CCTP V2.
Facts
- API
- Circle CCTP API
iris-api.circle.com - Kind
- Version retirement
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Circle CCTP API's own pages
Questions
When does this change take effect?
Circle CCTP API deprecated /v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Circle CCTP API has not given a shutdown date yet.
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.
More from Circle CCTP API 1
-
No date
GET /v2/fastBurn/USDC/fees/{}/{}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.