GET /v2/fastBurn/USDC/fees/{}/{} → endpoint removal
Circle CCTP API
Deprecated, no date
Circle deprecated the GET /v2/fastBurn/USDC/fees/{}/{} endpoint on June 10, 2025, without a shutdown date. Calls made to this endpoint will fail. This change impacts all integrations using this specific CCTP V2 API route.
Calls it hits
GET /v2/fastBurn/USDC/fees/{}/{}
What to use instead of these calls
Use GET /v2/burn/USDC/fees/{sourceDomainId}/{destDomainId}, which returns both Fast and Standard Transfer fees.
In Circle CCTP API's words
Deprecated the following CCTP V2 API endpoint:
Facts
- API
- Circle CCTP API
iris-api.circle.com - Kind
- Endpoint removal
- Announced
- June 10, 2025
- 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 GET /v2/fastBurn/USDC/fees/{}/{} 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
/v1/*Version retirement 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.