OpenSea API
/api/v1/* version retirement
Stopped workingSubscribe to OpenSea APIShare
On December 5, 2023, OpenSea shut down the V1 API. All calls to /api/v1/* endpoints fail and return 404 Not Found errors.
Calls it hits
/api/v1/*
What to use instead of these calls
Call the V2 API instead. Use GET /api/v2/chain/{chain}/contract/{address}/nfts/{identifier} for an NFT, GET /api/v2/collections/{slug} for a collection, or GET /api/v2/events for events.
In OpenSea API's words
On December 5th, OpenSea V1 API will be shut down. On this date, all V1 API requests will be return 404-Not Found errors.
Facts
- API
- OpenSea API
api.opensea.io - Kind
- Version retirement
- Announced
- October 4, 2023
- Takes effect
- December 5, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against OpenSea API's own pages
Questions
When does this change take effect?
Calls to /api/v1/* on OpenSea API stopped working on December 5, 2023.
What happens to calls after December 5, 2023?
They have failed since December 5, 2023.
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 OpenSea API 2
-
GET /api/v2/orders/{id}/{id}/listingsEndpoint removal Stopped working -
GET /api/v2/orders/{id}/{id}/offersEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.