/api → version retirement
Etherscan API
Stopped working
Calls to the /api endpoint will stop working on August 15, 2025. On that date, API V1 reaches full deprecation, causing all requests directed to this version to fail.
Calls it hits
/api
What to use instead of these calls
Send requests to the v2 endpoint at api.etherscan.io/v2/api using your existing module, action, and other query parameters. You must also supply the chainid parameter for the target chain, using an Etherscan API key that covers all supported chains.
In Etherscan API's words
API V1 will be fully deprecated by August 15, 2025 . After that, all V1 requests will stop working.
Facts
- API
- Etherscan API
api.etherscan.io - Kind
- Version retirement
- Announced
- July 30, 2025
- Takes effect
- August 15, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Etherscan API's own pages
Questions
When does this change take effect?
Calls to /api on Etherscan API stopped working on August 15, 2025.
What happens to calls after August 15, 2025?
They have failed since August 15, 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.