Today, we are launching two new endpoints: one endpoint to get the highest bid for an NFT and one endpoint to get the cheapest listing for an NFT.
Over the past 3 months, OpenSea has been closing the feature disparity between the V1 and V2 API. The V2 API is superior to V1 in many ways including:
Previously, OpenSea had been returning the OpenSea CDN url in NFT responses. One example is the List NFT endpoints which returned the NFT Model which included
image_url. Going forward, the
image_url field returned when listing NFTs, is deprecated.
There is a new guide created to help developers have clear instructions on what fees are required and how to set them when creating an order via the OpenSea API.
We've recently added a top level
chain field to most event payloads from the Stream API to make it easy to identify which chain the NFT or Collection affected by the event is on. The field has been added to following events:
At OpenSea, we believe in the continuing extensibility of NFT functionality and hope to continue to innovate with the community. There have been many new developments since ERC-721 was introduced in 2018, like ERC-1155 which introduced the notion of semi-fungible tokens. Today, we’re pleased to share ERC-7498 as a new standard for NFT redeemables.
Starting today, you will no longer be able to create new listings for or make new offers on BNB Smart Chain (BSC) NFTs.
We no longer return NFTs that are hidden from an account's profile page on our retrieve NFTs by account endpoint. NFTs are hidden by our systems automatically, or by users manually on their account page.
OpenSea API will no longer support API requests with non-versioned paths. Starting August 24th, all API requests must use one of the v1/ or v2/ prefixes to make API calls.
We are excited to announce the addition of a new field in the OpenSea API - the
encoded_token_ids field. It is present in the responses of our collection and trait offer read endpoints in the
criteria object - the new field is a concise and efficient way to represent a list of token ids that pertain to a given collection / trait offer. When decoded using the provided SDK function, developers can now see a list of all tokens that could be used to fulfill the offer.