OpenSea API
GET /api/v2/orders/{id}/{id}/listings endpoint removal
Stopped workingSubscribe to OpenSea APIShare
On May 7, 2026, the GET /api/v2/orders/{id}/{id}/listings endpoint was removed. Calls made to this endpoint fail after that date.
Calls it hits
GET /api/v2/orders/{id}/{id}/listings
What to use instead of these calls
Use GET /api/v2/listings/collection/{slug}/all instead. For a single order, use GET /api/v2/orders/chain/{chain}/protocol/{protocol_address}/{order_hash}.
In OpenSea API's words
We're cleaning up two deprecated REST API endpoints along with several response fields that have been marked deprecated for a while.
Facts
- API
- OpenSea API
api.opensea.io - Kind
- Endpoint removal
- Announced
- May 7, 2026
- Takes effect
- May 7, 2026
- 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 GET /api/v2/orders/{id}/{id}/listings on OpenSea API stopped working on May 7, 2026.
What happens to calls after May 7, 2026?
They have failed since May 7, 2026.
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
-
/api/v1/*Version retirement 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.