/blur/collections/search

POST /api/blur/collections/search

Price: 5 credits

Browse and rank Blur NFT collections by floor price or trading volume

How to use it

Browse and rank Blur NFT collections. Choose the ranking column (floor price; 15-minute, 1-day or 7-day trading volume; best standing collection bid) and the sort direction. Each row returns the collection name, slug, image, contract address, total supply and owner count, floor price (now, 1-day, 7-day), trading volume (15-minute, 1-day, 7-day), best standing collection bid and its total value, and best Blend loan offer (each with amount and unit). Pass a returned slug or contract address 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)
• sort string — Column to rank collections by (default: "VOLUME_ONE_DAY"; one of: "FLOOR_PRICE", "VOLUME_FIFTEEN_MINUTES", "VOLUME_ONE_DAY", "VOLUME_ONE_WEEK", "BEST_COLLECTION_BID")
• order string — Sort direction (default: "DESC"; one of: "ASC", "DESC")

Response

• @type string (default: "BlurCollection")
• contract_address string required
• name string nullable
• alias string nullable
• image string nullable
• total_supply integer nullable
• owner_count integer nullable
• floor_price object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• floor_price_1d object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• floor_price_7d object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• volume_15m object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• volume_1d object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• volume_7d object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• best_collection_bid object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• total_collection_bid_value object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• best_collection_loan_offer object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• trait_frequencies object nullable
  • * object
    • * integer

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.