/liquidation_com/lots/manifest

POST /api/liquidation_com/lots/manifest

Price: 20 credits

Get the item manifest of one Liquidation.com lot, open or closed: every line item with description, quantity, unit and extended retail price, and the identifiers, brand, model, condition and category columns the seller lists.

How to use it

Check what is inside a lot before bidding or to value a past sale. Columns differ by seller; any column without a named field is in other_fields, and any further table the seller adds, such as a grade legend, is in other_tables. total_quantity and total_retail_price are filled only when the manifest shows a totals row; otherwise sum line_items.

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, lot URL or manifest URL (examples: "21476932", "https://www.liquidation.com/auction/view?id=21476932", "https://www.liquidation.com/aucimg/21476/m21476932.html"; minLength: 1)

Response

• @type string (default: "LiquidationComManifest")
• id string required
• url string required
• lot_url string required
• columns array (default: [])
• line_items array (default: [])
  • @type string (default: "LiquidationComManifestItem")
  • description string nullable
  • quantity integer nullable
  • retail_price number nullable
  • total_retail_price number nullable
  • upc string nullable
  • sku string nullable
  • asin string nullable
  • fnsku string nullable
  • lpn string nullable
  • brand string nullable
  • model string nullable
  • color string nullable
  • condition string nullable
  • category string nullable
  • subcategory string nullable
  • notes string nullable
  • serial_number string nullable
  • other_fields array (default: [])
    • @type string (default: "LiquidationComManifestField")
    • name string required
    • value string required
• line_items_count integer required
• total_quantity integer nullable
• total_retail_price number nullable
• other_tables array (default: [])
  • @type string (default: "LiquidationComManifestTable")
  • columns array (default: [])
  • rows array (default: [])
    • @type string (default: "LiquidationComManifestTableRow")
    • fields 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 — This lot has no manifest 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.