/sothebys/shop/items

POST /api/sothebys/shop/items

Price: 1 credit

Get one Sotheby's buy-now or private-sale item by id, slug or URL: title, creators, description, condition, price or minimum offer, availability, object details with dimensions, shipping origin and destinations, variants and images.

How to use it

Fetch a Sotheby's marketplace item by the id from sothebys/shop/search, sothebys/private_sales/search or a buy-now or private-sale result of sothebys/lots/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• item string required — Sotheby's shop or private-sale item id, slug or URL (examples: "3bc08395-ba58-4ac5-9824-2fbb682c34aa", "https://www.sothebys.com/en/buy/pdp/fine-art/print/_raymond-pettibon-hc-no-title-but-the-sand-3d55", "pablo-picasso-the-workshop-89ea"; minLength: 1)

Response

• @type string (default: "SothebysShopItem")
• id string required
• url string nullable
• alias string nullable
• sku string nullable
• creators array (default: [])
• attribution string nullable
• guarantee_line string nullable
• sale_designation string nullable
• description string nullable
• catalogue_note string nullable
• condition_grade integer nullable
• condition_notes string nullable
• property_type string nullable
• department string nullable
• categories array (default: [])
• tags array (default: [])
• images array (default: [])
• currency string nullable
• price number nullable
• estimated_retail_price number nullable
• min_offer number nullable
• is_available boolean nullable
• available_quantity integer nullable
• is_owned boolean nullable
• is_buy_now_enabled boolean nullable
• is_offer_enabled boolean nullable
• is_enquiry_enabled boolean nullable
• manager_email string nullable
• sales_entity string nullable
• objects array (default: [])
  • @type string (default: "SothebysItemObject")
  • object_type string nullable
  • is_sothebys_approved boolean nullable
  • provenance string nullable
  • exhibition string nullable
  • literature string nullable
  • attributes array (default: [])
    • @type string (default: "SothebysItemAttribute")
    • name string nullable
    • values array (default: [])
    • unit string nullable
  • dimensions array (default: [])
    • @type string (default: "SothebysItemAttribute")
    • name string nullable
    • values array (default: [])
    • unit string nullable
• has_free_shipping boolean nullable
• ships_internationally boolean nullable
• ships_from_city string nullable
• ships_from_state string nullable
• ships_from_country string nullable
• shipping_destinations array (default: [])
• shipping_services array (default: [])
• variant_group string nullable
• variants array (default: [])
  • @type string (default: "SothebysItemVariant")
  • id string nullable
  • sku string nullable
  • value string nullable
  • group_name string nullable
  • price number nullable
  • available_quantity integer nullable
  • is_available boolean 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 Sotheby's shop item exists at this id, slug 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.