/blur/collections/traits

POST /api/blur/collections/traits

Price: 5 credits

List trait values of a Blur collection with per-trait floor, last sale and bid stats

How to use it

List the trait values of a Blur collection, identified by its slug (e.g. 'azuki') or contract address. Each row returns a trait category and value with its last sale price, current floor price, best standing bid price and total bid value (each with amount and unit). These are the per-trait market analytics used to price individual NFTs.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• collection string required — Collection slug (e.g. 'azuki') or its on-chain contract address (examples: "azuki", "0xed5af388653567af2f388e6224dc7c4b3241c544"; minLength: 1)
• count integer required — Number of trait values to return (min: 1)

Response

• @type string (default: "BlurTrait")
• category string required
• value string required
• sale object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• floor object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• best_bid_price object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• total_bid_value object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string 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 — Collection 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.

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.