/liquidation_com/lots

POST /api/liquidation_com/lots

Price: 10 credits

Get one Liquidation.com lot by id: title, current or winning bid, close time, bid counters, condition, quantity and retail value, shipping details, category, full description, photo gallery and the seller's rating.

How to use it

Read a wholesale lot before bidding. Pass the id of an open lot from liquidation_com/lots/search; its item list is liquidation_com/lots/manifest.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• lot string required — Liquidation.com lot (auction) id or lot URL (examples: "21493554", "https://www.liquidation.com/auction/view?id=21493554"; minLength: 1)

Response

• @type string (default: "LiquidationComLot")
• id string required
• url string required
• manifest_url string nullable
• is_closed boolean required
• closes_at integer nullable
• current_bid number nullable
• currency string nullable
• savings_percent number nullable
• minimum_bid number nullable
• buy_now_price number nullable
• is_sealed_bid boolean required
• views_count integer nullable
• bids_count integer nullable
• bidders_count integer nullable
• watchers_count integer nullable
• location string nullable
• fulfilled_by string nullable
• seller object nullable
  • @type string (default: "LiquidationComSellerRating")
  • id string nullable
  • alias string nullable
  • name string required
  • url string nullable
  • is_marketplace_seller boolean required
  • selling_since_date string nullable
  • lifetime_completed_transactions string nullable
  • recent_completed_transactions string nullable
  • cancelled_transactions_percent number nullable
  • cancelled_transactions_stars integer nullable
  • average_days_to_ship number nullable
  • shipping_time_stars integer nullable
  • honored_disputes_percent number nullable
  • honored_disputes_stars integer nullable
• condition string nullable
• auction_type string nullable
• quantity integer nullable
• quantity_variance_percent number nullable
• retail_price_per_unit number nullable
• bid_price_per_unit number nullable
• buyers_premium_percent number nullable
• shipping_terms string nullable
• total_weight_lbs number nullable
• dimensional_weight_lbs number nullable
• minimum_shipping_fee number nullable
• postal_code string nullable
• size_classification string nullable
• packages_count integer nullable
• package_type string nullable
• available_lots_count integer nullable
• shipping_restrictions string nullable
• category object nullable
  • @type string (default: "LiquidationComCategory")
  • id string nullable
  • name string required
  • url string nullable
• subcategories array (default: [])
  • @type string (default: "LiquidationComCategory")
  • id string nullable
  • name string required
  • url string nullable
• description string nullable
• images array (default: [])
• other_specs array (default: [])
  • @type string (default: "LiquidationComSpec")
  • name string required
  • value string required

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 lot with this id is listed on Liquidation.com 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.