allsurplus.com APIallsurplus.com ↗
Access AllSurplus B2B surplus auction data: search assets, get lot details, list auction events, and browse category/location hierarchies via 6 endpoints.
curl -X POST 'https://api.parse.bot/scraper/f6ee20f8-b2d1-4a4d-be82-cae28e1ded7c/search_assets' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"page": "1",
"limit": "5",
"query": "truck",
"sort_field": "bestfit",
"sort_order": "desc"
}'Search and browse auction lots (assets) with various filters. Returns paginated results including asset details, facets for filtering, and total count.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| limit | integer | Number of results per page. |
| query | string | Search keyword. Use '*' for all results. |
| event_id | string | Event ID to filter results by a specific auction event. |
| time_type | string | Time-based filter such as 'closingToday' or 'newListings'. |
| sort_field | string | Field to sort by: 'bestfit', 'closedatetime', 'currentbid'. |
| sort_order | string | Sort order: 'asc' or 'desc'. |
| account_ids | string | Comma-separated list of numeric account IDs to filter by seller. |
| category_ids | string | Category ID to filter results (from list_categories endpoint). |
| facets_filter | string | JSON array of facet filter strings (e.g. '["region:\"Americas\""]'). |
{
"type": "object",
"fields": {
"total": "integer total number of matching assets",
"assets": "array of asset objects with fields like assetId, accountId, assetShortDescription, currentBid, locationCity, locationState, country, assetAuctionEndDate",
"facets": "array of facet objects for further filtering"
},
"sample": {
"data": {
"total": 7030,
"assets": [
{
"model": "M2 106",
"assetId": 13,
"country": "USA",
"accountId": 28701,
"makebrand": "Freightliner",
"modelYear": "2016",
"currentBid": 11000,
"currencyCode": "USD",
"locationCity": "Phoenix",
"locationState": "AZ",
"timeRemaining": "7:20:12:44",
"assetAuctionEndDate": "2026-05-21T19:00:00",
"categoryDescription": "Bucket Trucks",
"assetShortDescription": "Altec LR758 Bucket Mtd on 2016 Freightliner M2 106 S/A Bucket Truck"
}
],
"facets": []
},
"status": "success"
}
}About the allsurplus.com API
The AllSurplus API exposes 6 endpoints covering industrial and surplus auction data from allsurplus.com, including asset search, full lot details, and auction event schedules. The search_assets endpoint returns paginated results with current bid prices, location fields, and facets for filtering by seller, category, or time window. get_asset_detail delivers photos, long descriptions, brand/model fields, and structured attribute groups for any individual lot.
Asset Search and Filtering
The search_assets endpoint accepts keyword queries, pagination controls (page, limit), and filters including event_id, time_type (e.g. closingToday, newListings), and account_ids for seller-specific results. Results include an assets array with fields like assetId, accountId, assetShortDescription, currentBid, locationCity, locationState, and country, plus a facets array you can pass back as filters on subsequent requests. The total field gives you the full result count before pagination.
Lot Details and Auction Events
get_asset_detail requires both asset_id and account_id (both returned by search_assets) and returns the full lot record: assetLongDesc, assetShortDesc, makebrand, model, geographic fields, currentBid, assetPhotos (array of photo URL paths), and assetAttributeGroups — structured arrays of named attribute groups with key-value pairs that encode specs, condition, and other lot metadata.
For auction scheduling, list_auction_events returns paginated event records with saleEventId, saleEventTitle, open and close datetimes, and asset counts. You can apply facets_filter as a JSON array of filter strings to narrow by event type. get_auction_event_detail returns the full event record including importantNotice, contactDetails, and saleEventDescription as HTML strings, plus timeRemaining until close.
Category and Location Hierarchies
list_categories and list_locations both return nested menus arrays with no required inputs. Categories follow a three-level hierarchy (L0 > L1 > L2); each node carries a menuId, menuDescription, and asset count. The locations hierarchy mirrors this structure, nesting countries and states under top-level regions — useful for building browse-by-location interfaces or pre-filtering search_assets calls.
- Monitor
currentBidacross lots matching a keyword to track price trends in specific equipment categories. - Build an auction calendar feed using
list_auction_eventsfiltered by close date and enriched withget_auction_event_detailcontact and notice fields. - Aggregate seller inventory by passing specific
account_idstosearch_assetsto see all lots from a given liquidator. - Populate a category-browse UI from
list_categorieshierarchy data with live asset counts at each node. - Alert on new surplus listings in a target geography using
time_type: newListingscombined with state/country filters fromlist_locations. - Extract structured equipment specs from
assetAttributeGroupsinget_asset_detailfor comparison or cataloging workflows. - Identify closing-soon lots by sorting
search_assetsresults byclosedatetimeascending withtime_type: closingToday.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does AllSurplus have an official developer API?+
What does `get_asset_detail` return beyond what `search_assets` includes?+
search_assets returns a summary record per lot including assetShortDescription, currentBid, and location fields. get_asset_detail adds assetLongDesc, makebrand, model, the full assetPhotos array, and assetAttributeGroups — structured attribute data that typically encodes specifications, condition notes, and other lot-level metadata not present in search results.Can I retrieve bid history or individual bidder data for a lot?+
currentBid in both search_assets and get_asset_detail, but does not expose bid history, bid increments, or bidder identities. You can fork this API on Parse and revise it to add an endpoint targeting that data if it becomes accessible.How does pagination work across endpoints that support it?+
search_assets and list_auction_events both accept page and limit parameters. The total field in each response gives the full matched count, so you can compute the number of pages as ceil(total / limit). list_categories and list_locations return complete hierarchies in a single call with no pagination.Does the API expose seller contact information or payment/removal terms?+
get_asset_detail for individual lots. Seller contact details at the event level are returned by get_auction_event_detail as the contactDetails HTML field. Direct seller contact records beyond what those fields contain are not currently exposed. You can fork the API on Parse and revise it to surface additional seller-level fields if they are available.