/blur/activity/search

POST /api/blur/activity/search

Price: 1 credit

List recent marketplace activity (sales, listings, transfers) for a Blur collection

How to use it

List recent marketplace activity for a Blur collection, identified by its slug (e.g. 'azuki') or contract address, optionally filtered to specific event types (sale, listing, transfer). Each event returns its id, token id and image, event type, price (amount and unit), the from/to trader addresses, the timestamp, transaction hash, marketplace and maker side.

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 activity events to return (min: 1; max: 100)
• event_types array nullable — Filter to specific event types; all event types are included when omitted (one of: "sale", "orderCreated", "transfer")

Response

• @type string (default: "BlurActivity")
• id string required
• contract_address string nullable
• token_id string nullable
• image string nullable
• event_type string nullable
• price object nullable
  • @type string (default: "BlurPrice")
  • amount number nullable
  • unit string nullable
  • listed_at string nullable
  • marketplace string nullable
• from_trader object nullable
  • @type string (default: "BlurTrader")
  • address string required
  • username string nullable
• to_trader object nullable
  • @type string (default: "BlurTrader")
  • address string required
  • username string nullable
• created_at string nullable
• transaction_hash string nullable
• marketplace string nullable
• maker_side 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.