Okapi Okapi

Arbiscan API /api version retirement

Stopped workingSubscribe to Arbiscan APIShare

Calls to /api on Arbiscan API stopped working on August 15, 2025.


Calls it hits

  • /api

What to use instead of these calls

Call api.etherscan.io/v2/api with the same module, action, and other query parameters, and include chainid for the chain. An Etherscan API key covers every supported chain.

In Arbiscan API's words

API V1 will be fully deprecated by August 15, 2025 . After that, all V1 requests will stop working.

Arbiscan API, Announcement

Facts

API
Arbiscan API api.arbiscan.io
Kind
Version retirement
Announced
July 30, 2025
Takes effect
August 15, 2025
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Arbiscan API's own pages

Questions

When does this change take effect?

Calls to /api on Arbiscan 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.

Add to GitHub

Get notifications

Subscribe to Arbiscan API

Hear about each breaking change Arbiscan API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Arbiscan API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.