/artprice/sales

POST /api/artprice/sales

Price: 10 credits

Get an upcoming Artprice partner auction sale by id or URL: title, dates, auction house with address and contacts, viewing times, lot categories, and its lots with artist, technique, dimensions, estimate and pictures, in catalogue order.

How to use it

Fetch an Artprice partner sale by the id in artprice.com/sale/<id>/<title>, with up to lots_count of its lots. Only partner sales open; artprice/lots returns the sale_id of a partner lot. Pass a lot id to artprice/lots for the lot's full description.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• sale string required — Artprice sale id or sale page URL (examples: "576327", "https://www.artprice.com/sale/576327/irish+%26+international+art"; minLength: 1)
• lots_count integer required — Max number of the sale's lots to return (min: 0)

Response

• @type string (default: "ArtpriceSale")
• id string required
• url string nullable
• image string nullable
• schedule string nullable
• start_date string nullable
• end_date string nullable
• sale_type string nullable
• country string nullable
• city string nullable
• auctioneer_id string nullable
• auctioneer_name string nullable
• auctioneer_address string nullable
• auctioneer_phone string nullable
• auctioneer_fax string nullable
• auctioneer_email string nullable
• auctioneer_website_url string nullable
• expositions array (default: [])
• lot_count integer nullable
• lot_categories array (default: [])
  • @type string (default: "ArtpriceCategoryCount")
  • id string required
  • name string nullable
  • count integer nullable
• lots array (default: [])
  • @type string (default: "ArtpriceSaleLot")
  • id string required
  • url string nullable
  • number string nullable
  • artist_id string nullable
  • artist_name string nullable
  • category string nullable
  • technique string nullable
  • dimensions string nullable
  • edition string nullable
  • creation_date string nullable
  • estimate_low number nullable
  • estimate_high number nullable
  • estimate_currency string nullable
  • start_date string nullable
  • end_date string nullable
  • country string nullable
  • city string nullable
  • auctioneer_name string nullable
  • auctioneer_lot_url string nullable
  • is_past boolean nullable
  • image string nullable
  • images array (default: [])

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 sale 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.