/opensea/tokens/search

POST /api/opensea/tokens/search

Price: 5 credits

Browse and rank fungible tokens traded on OpenSea (trending, top, new)

How to use it

Browse and rank the fungible tokens traded on OpenSea. Choose the tab (trending, top or new) and optionally restrict to specific blockchains. Each token returns its contract address, chain, name, symbol, image, current USD price, market cap, total supply, verification status, and price change and volume across the 1h, 24h, 7d and 30d windows. Pass a returned contract address and chain to the 'tokens' endpoint for full details.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Number of tokens to return (min: 1)
• tab string — Ranking tab to browse (default: "trending"; one of: "trending", "top", "new")
• chains array nullable — Restrict to tokens 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")

Response

• @type string (default: "OpenseaToken")
• contract_address string required
• chain string nullable
• name string nullable
• symbol string nullable
• decimals integer nullable
• image string nullable
• usd_price number nullable
• market_cap_usd number nullable
• total_supply number nullable
• is_verified boolean (default: false)
• is_native boolean (default: false)
• token_group string nullable
• score number nullable
• genesis_date string nullable
• created_at string nullable
• price_change_1h number nullable
• price_change_24h number nullable
• price_change_7d number nullable
• price_change_30d number nullable
• volume_1h number nullable
• volume_24h number nullable
• market_cap_change_24h number nullable
• warnings array (default: [])

Errors

• 422 — 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 — The entity was not found, or a precondition failed 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.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-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.