/christies/auctions

POST /api/christies/auctions

Price: 10 credits

Get one Christie's auction, live or online, by id or URL: title, sale number, location, start and end time, sessions, registration deadline, lot count and the sale total once the auction has closed.

How to use it

Fetch a Christie's auction by the sale id found in a lot's sale or in a christies.com/en/auction URL. Use christies/auctions/lots for its lots.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• auction string required — Christie's auction id or auction URL (examples: "31076", "https://www.christies.com/en/auction/auction-31076", "https://onlineonly.christies.com/s/japanese-art-online/4115"; minLength: 1)

Response

• @type string (default: "ChristiesAuction")
• id string required
• sale_number string nullable
• online_sale_id string nullable
• room_code string nullable
• sale_type string nullable
• sale_type_text string nullable
• location string nullable
• url string nullable
• image string nullable
• start_at integer nullable
• end_at integer nullable
• start_time_zone string nullable
• end_time_zone string nullable
• date_text string nullable
• registration_close_at integer nullable
• is_registration_allowed boolean nullable
• is_in_progress boolean nullable
• is_over boolean nullable
• lot_count integer nullable
• currency string nullable
• total_sold number nullable
• total_sold_text string nullable
• results_url string nullable
• sessions array (default: [])
  • @type string (default: "ChristiesAuctionSession")
  • time_text string nullable
  • lots_text string nullable
  • start_at integer 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 Christie's auction exists at this id or URL. 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.