/artprice/lots

POST /api/artprice/lots

Price: 1 credit

Get an upcoming Artprice auction lot by id or URL: title, artist, lot number, category, technique, dimensions, estimate in the sale currency and ten converted currencies, signature, provenance and literature notes, pictures, and the sale with its auction house.

How to use it

Fetch an upcoming Artprice lot by the numeric lot id in its URL. Lots in partner sales open; most other lots answer 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Artprice lot id or lot page URL (examples: "43593888", "https://www.artprice.com/artist/168756/ciaran-clear/painting/43593888/november-night"; minLength: 1)

Response

• @type string (default: "ArtpriceLot")
• id string required
• url string nullable
• number string nullable
• artist object nullable
  • @type string (default: "ArtpriceArtistRef")
  • id string required
  • alias string nullable
  • name string nullable
  • dates string nullable
  • url string nullable
  • image string nullable
  • member_ids array nullable
• category string nullable
• technique string nullable
• dimensions_in string nullable
• dimensions_cm string nullable
• estimate_text string nullable
• estimates array (default: [])
  • @type string (default: "ArtpriceEstimate")
  • currency string required
  • low number nullable
  • high number nullable
• details array (default: [])
• images array (default: [])
• sale_id string nullable
• sale_url string nullable
• sale_title string nullable
• sale_start_date string nullable
• sale_end_date string nullable
• sale_country string nullable
• auctioneer_id string nullable
• auctioneer_name string nullable
• auctioneer_address 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 — The lot does not exist or its page is open to subscribers only. 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.