/catawiki/lots/bids

POST /api/catawiki/lots/bids

Price: 1 credit

List the bids placed on a Catawiki lot, newest first: amount in EUR, USD or GBP, time, and the bidder's anonymised label, stable token and country.

How to use it

Get a Catawiki lot's bid history by lot id or URL. The bidder token matches the highest_bidder_token and winner_token of catawiki/lots.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Catawiki lot id or lot URL (examples: "107069105", "https://www.catawiki.com/en/l/107069105-rolex-datejust-16233-unisex-1989"; minLength: 1)
• currency string — Currency of the bid amounts (default: "EUR"; one of: "EUR", "USD", "GBP")
• count integer required — Max number of bids to return (min: 1)

Response

• @type string (default: "CatawikiBid")
• id string required
• lot_id string required
• amount number nullable
• currency string nullable
• created_at integer nullable
• bidder_name string nullable
• bidder_token string nullable
• bidder_total_bid_count integer nullable
• bidder_country_code string nullable
• is_from_order boolean nullable
• explanation_type 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 — No Catawiki lot exists at this id. 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.