# /liquidation_com/lots/search

`POST /api/liquidation_com/lots/search`

Price: 20 credits

Search Liquidation.com wholesale lots by keyword, seller, category, condition, lot size, region, warehouse, price, bids, shipping terms and auction format, optionally including closed auctions: each with current or final bid, estimated retail value, close time, seller, location and lot size.

## How to use it

Find wholesale liquidation lots to bid on. With no filter it lists every open lot. Pass the id of an open result to liquidation_com/lots for the full record, and any result id to liquidation_com/lots/manifest for the item list.

## Parameters

- `access-token` (string, required)

## Request body

- `timeout` (integer) — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
- `count` (integer, required) — Max number of lots to return (min: 1; max: 2000)
- `keyword` (string, nullable) — Words to search for (examples: "laptop"; minLength: 1; maxLength: 200)
- `keyword_mode` (string) — Match all words, any word, or the exact phrase (default: "all"; one of: "all", "any", "exact")
- `search_description` (boolean) — Match the keyword in the lot description as well as the title (default: true)
- `seller` (string, nullable) — Seller name (examples: "IZZYSALES", "Titan Returns"; minLength: 1)
- `include_closed` (boolean) — Include closed auctions with their final bid (default: false)
- `categories` (array) — Categories, any of (default: []; one of: "appliances", "clothing_accessories", "computers_networking", "consumer_electronics", "furniture", "general_merchandise", "health_beauty", "holiday_seasonal", "home_improvement", "housewares", "jewelry_watches", "mystery_box", "tools_machinery")
- `conditions` (array) — Conditions, any of (default: []; one of: "new", "used", "refurbished", "returns", "shelf_pulls", "salvage", "damaged", "scratch_and_dent")
- `lot_sizes` (array) — Lot sizes, any of (default: []; one of: "package", "pallet", "truckload", "large_item")
- `regions` (array) — US regions, any of (default: []; one of: "northeast", "midwest", "west", "south", "available_for_export")
- `warehouses` (array) — Warehouses, any of (default: []; one of: "garland_tx", "las_vegas_nv", "brownsburg_in", "brampton_on", "north_wilkesboro_nc", "cincinnati_oh", "pittston_pa")
- `retail_price_ranges` (array) — Estimated retail value ranges in USD, any of (default: []; one of: "under_500", "500_to_1499", "1500_to_2999", "3000_to_9999", "over_10000")
- `lot_price_ranges` (array) — Current bid ranges in USD, any of (default: []; one of: "under_100", "100_to_200", "200_to_300", "300_to_500", "500_to_1000", "over_1000")
- `bids` (array) — Number of bids, any of (default: []; one of: "no_bids", "one_bid", "two_to_five_bids", "over_five_bids", "sealed_bid")
- `shipping_terms` (array) — Shipping terms, any of (default: []; one of: "pickup_only", "liquidation_arranges", "buyer_must_arrange", "buyer_may_arrange", "seller_arranges")
- `auction_types` (array) — Auction formats, any of (default: []; one of: "standard", "fixed_price", "sealed_bid", "mixed_format")
- `sort` (string) — Sort field (default: "relevance"; one of: "relevance", "close_time", "open_time", "current_bid", "items_count", "title", "state")
- `sort_order` (string) — Sort direction (default: "desc"; one of: "asc", "desc")

## Response

### 200 — Successful Response

- `@type` (string) (default: "LiquidationComLotCard")
- `id` (string, required)
- `url` (string, required)
- `image` (string, nullable)
- `is_closed` (boolean, required)
- `closes_at` (integer, nullable)
- `current_bid` (number, nullable)
- `is_sealed_bid` (boolean, required)
- `retail_price` (number, nullable)
- `bids_count` (integer, nullable)
- `views_count` (integer, nullable)
- `watchers_count` (integer, nullable)
- `seller_name` (string, nullable)
- `location` (string, nullable)
- `condition` (string, nullable)
- `packages_count` (integer, nullable)
- `package_type` (string, nullable)
- `items_count` (integer, nullable)

## Errors

### 422 — Validation Error

The request body did not validate

What to do: Check the fields against this schema. A URN with the wrong prefix is the most common cause.

- `detail` (array)
  - `loc` (array, required)
  - `msg` (string, required)
  - `type` (string, required)
  - `input` (any)
  - `ctx` (object)

### 408

The request ran past its time limit

What to do: 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 entity was not found, or a precondition failed

What to do: 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

What to do: 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

What to do: 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

What to do: Wait at least 30 seconds, then retry.

## Response envelope

Success: Array of objects (may be empty if no results)

Error: Error may coexist with partial results if it occurs mid-execution. Check X-Error header and status code.

Every response carries these 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.