/api → version retirement
BscScan API
Stopped working
On August 15, 2025, the /api endpoint will stop working as API V1 reaches full deprecation. Requests made to this endpoint after that day will fail. The change affects all callers sending requests to the V1 interface.
Calls it hits
/api
What to use instead of these calls
Send requests to the V2 API endpoint instead, keeping the existing module, action, and other query parameters while adding chainid for the target chain. An Etherscan API key covers every supported chain.
In BscScan API's words
API V1 will be fully deprecated by August 15, 2025 . After that, all V1 requests will stop working.
Facts
- API
- BscScan API
api.bscscan.com - Kind
- Version retirement
- Announced
- July 30, 2025
- Takes effect
- August 15, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against BscScan API's own pages
Questions
When does this change take effect?
Calls to /api on BscScan 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.