I’m trying to figure out the cancel event type in the Opensea API. Most responses include details about the NFT being canceled, but some don’t. Here’s an example of a typical response:
Having worked extensively with the OpenSea API, I can shed some light on this issue. The ‘nft’:null occurrences typically relate to bundle listings or collection offers. In these cases, the cancellation isn’t tied to a specific NFT, hence the null value. It’s also possible for this to happen with orders involving fungible tokens like WETH.
To get more clarity, I’d recommend examining the ‘order_type’ field in these responses. If it’s a ‘criteria’ type, that usually indicates a collection offer. For bundle listings, you might need to query additional endpoints to retrieve the full order details.
This null field isn’t a bug per se, but rather a reflection of the diverse order types OpenSea supports. Always ensure your code can handle these null cases gracefully.
ooh interesting question kai! i’ve been playing around with the opensea api too and noticed that weird null nft thing. have you tried digging into the order details for those null cases? maybe there’s some clue there about what’s being cancelled.
i wonder if it could be related to non-nft orders, like when someone lists eth for weth or something? or maybe it’s a glitch in the matrix lol.
what kinda project are u working on with the api? sounds pretty cool. have u found any other quirks or oddities while exploring the data?
hey kai, i’ve seen this too. it appears null nft field occurs with bundle listings or when nft details are missing, perhaps for collection offers. maybe a system glitch. just my 2 cents.