On June 27th, 2023, we released 4 new endpoints under our /v2 schema:

Today, OpenSea has launched 2 new events in the Stream API. The new events will be emitted when orders, both listings and offers, have been invalidate or revalidated. Emitting these events will allow marketplace aggregators and other consumers who are maintaining a copy of the OpenSea order book to more easily ensure the orders are executable.

OpenSea has been hard at work helping to build the API to be valuable to the broader Web3 ecosystem. Here are some of the ways, the API has changed this week.

OpenSea has been hard at work helping to build the API to be valuable to the broader Web3 ecosystem. Here are some of the ways, the API has changed this week:

OpenSea has been hard at work helping to build the API to be valuable to the broader Web3 ecosystem. Here are some of the ways, the API has changed this week:

OpenSea has been hard at work helping to build the API to be valuable to the broader Web3 ecosystem. Here are some of the ways, the API has changed this week:

A couple weeks ago, we posted an RFC about a proposal to update our bidding precision logic. Thank you for all of your feedback. The final decision is listed below with all rationale. Thank you again for being so engaged with us.

OpenSea has been hard at work helping to build the API to be valuable to the broader Web3 ecosystem. Here are some of the ways, the API has changed this week:

Seaport 1.5 is released and currently being used by all new orders on the OpenSea website.
Developers have a 7 day deadline, May 9th, to make the changes required. On May 9th, all future orders using Seaport 1.4 will be rejected.

A couple weeks ago, we announced an update to our bidding precision rules. We heard loudly from our developer community that these changes would negatively impact bidding on items on OpenSea. We want to make sure we incorporate your feedback into these changes, so we're presenting our plan here as a Request for Comment ahead of the proposed go-live.