/blur/collections/charts

POST /api/blur/collections/charts

Price: 1 credit

Get the floor-price and sales time series for a Blur collection

How to use it

Get the floor-price and sales time series for a Blur collection, identified by its slug (e.g. 'azuki') or contract address, over a chosen time span (day, week or month). Each interval returns its open and close timestamps (in milliseconds), the closing and low floor price with marketplace, and the individual sales in that interval (token id, price, marketplace and timestamp).

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 time intervals to return (min: 1)
• window string — Time span of the chart (default: "day"; one of: "day", "week", "month")

Response

• @type string (default: "BlurChartInterval")
• opened_at integer nullable
• closed_at integer nullable
• floor_close_price number nullable
• floor_close_marketplace string nullable
• floor_low_price number nullable
• sales array (default: [])
  • @type string (default: "BlurChartSale")
  • created_at integer nullable
  • token_id string nullable
  • price number 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.