/opensea/collections/search

POST /api/opensea/collections/search

Price: 10 credits

Rank and list OpenSea NFT collections by trading score (trending or top) over a time window

How to use it

Browse and rank OpenSea NFT collections. Choose the tab (trending or top), the time window (1m, 5m, 15m, 1h, 1d, 7d, 30d or all-time) and optionally restrict to a single category (art, gaming, memberships, music, photography, domain names, sports, physical, virtual worlds or PFPs). Each row returns the collection slug, name, image, chain, verification status, ranking score, floor price and top offer, and rolling stats (owner count, total supply, listed count, and volume/sales/floor-price change across the 1h, 1d, 7d and 30d windows). Pass a returned slug to the 'collections' endpoint for the full profile.

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 collections to return (min: 1)
• tab string — Ranking tab to browse (default: "trending"; one of: "trending", "top")
• timeframe string — Time window for the ranking metrics (default: "one_day"; one of: "one_minute", "five_minute", "fifteen_minute", "one_hour", "one_day", "seven_days", "thirty_days", "all")
• category string nullable — Restrict the ranking to a single category (one of: "art", "gaming", "memberships", "music", "photography", "domain_names", "sports_collectibles", "physical_collectibles", "virtual_worlds", "pfps")

Response

• @type string (default: "OpenseaCollectionRank")
• slug string required
• name string nullable
• image string nullable
• chain string nullable
• is_verified boolean (default: false)
• score number nullable
• metadata_storage string nullable
• created_at string nullable
• floor_price object nullable
  • @type string (default: "OpenseaPrice")
  • usd number nullable
  • amount number nullable
  • symbol string nullable
  • native number nullable
• top_offer object nullable
  • @type string (default: "OpenseaPrice")
  • usd number nullable
  • amount number nullable
  • symbol string nullable
  • native number nullable
• stats object nullable
  • @type string (default: "OpenseaCollectionStats")
  • owner_count integer nullable
  • sales integer nullable
  • total_supply integer nullable
  • unique_item_count integer nullable
  • listed_item_count integer nullable
  • volume_usd number nullable
  • volume_native number nullable
  • one_hour object nullable
    • @type string (default: "OpenseaWindowStats")
    • volume_usd number nullable
    • volume_native number nullable
    • sales integer nullable
    • floor_price_change number nullable
  • one_day object nullable
    • @type string (default: "OpenseaWindowStats")
    • volume_usd number nullable
    • volume_native number nullable
    • sales integer nullable
    • floor_price_change number nullable
  • seven_days object nullable
    • @type string (default: "OpenseaWindowStats")
    • volume_usd number nullable
    • volume_native number nullable
    • sales integer nullable
    • floor_price_change number nullable
  • thirty_days object nullable
    • @type string (default: "OpenseaWindowStats")
    • volume_usd number nullable
    • volume_native number nullable
    • sales integer nullable
    • floor_price_change number nullable

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.