POST /api/opensea/accounts/items
Price: 10 credits
List the NFTs held by an OpenSea account (wallet address, username or ENS name)
List the NFTs held by an OpenSea account, identified by a wallet address, OpenSea username or ENS name. Filter by listing status (all, listed or not listed) and by blockchains, and sort by offer, listed price, floor, cost, last sale, rarity, or received / listed / created date. Each item returns its chain, contract address and token id, name and image, parent collection (slug, name, floor price), token standard, rarity rank, last sale, best listing and best offer (in native, token and USD), owner and traits.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)identifier string required — Account identifier: a wallet address, OpenSea username or ENS name (examples: "pranksy", "vitalik.eth", "0xd387a6e4e84a6c86bd90c158c6028a58cc8ac459"; minLength: 1)count integer required — Number of items to return (min: 1)status string — Listing status filter (default: "all"; one of: "all", "listed", "not_listed")sort string — Sort order (default: "highest_offer"; one of: "highest_offer", "lowest_offer", "recently_received", "oldest_received", "highest_listed_price", "lowest_listed_price", "most_rare", "least_rare", "highest_floor", "lowest_floor", "highest_cost", "lowest_cost", "highest_last_sale", "recently_listed", "recently_created")chains array nullable — Restrict to NFTs on these blockchains (one of: "ethereum", "base", "solana", "arbitrum", "optimism", "polygon", "abstract", "monad", "ink", "apechain", "megaeth", "soneium", "somnia", "animechain", "avalanche", "b3", "berachain", "blast", "flow", "gunz", "ronin", "sei", "shape", "unichain", "zora", "hyperevm")@type string (default: "OpenseaItem")chain string nullablecontract_address string requiredtoken_id string requiredname string nullableimage string nullableanimation_url string nullabledescription string nullablestandard string nullableis_fungible boolean (default: false)total_supply integer nullablerarity_rank integer nullablerarity_category string nullableimage_aspect_ratio number nullablebackground_color string nullabletoken_uri string nullablemetadata_storage string nullableowner string nullablelast_sale object nullable@type string (default: "OpenseaPrice")usd number nullableamount number nullablesymbol string nullablenative number nullablebest_listing object nullable@type string (default: "OpenseaListing")price object nullable@type string (default: "OpenseaPrice")usd number nullableamount number nullablesymbol string nullablenative number nullablemarketplace string nullablemaker string nullablequantity_remaining integer nullablestart_time string nullableend_time string nullablebest_offer object nullable@type string (default: "OpenseaPrice")usd number nullableamount number nullablesymbol string nullablenative number nullablecollection object nullable@type string (default: "OpenseaItemCollection")slug string requiredname string nullableimage string nullablecategory string nullableexternal_url string nullabletwitter string nullableinstagram string nullablediscord string nullablestandard string nullableis_verified boolean (default: false)floor_price object nullable@type string (default: "OpenseaPrice")usd number nullableamount number nullablesymbol string nullablenative number nullableattributes array (default: [])@type string (default: "OpenseaItemTrait")trait_type string requiredvalue string requiredcreated_at string nullablelast_sale_at string nullablelast_transfer_at string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — Account not found Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.