autobidmaster.com APIautobidmaster.com ↗
Access AutoBidMaster (Copart) auction inventory via API. Search vehicles, get lot details, damage types, body styles, makes, and sale locations.
curl -X GET 'https://api.parse.bot/scraper/c6fd4d1b-7ed8-49b8-b5f2-a977ec97f6ed/search_vehicles?make=toyota&page=1&size=3' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for vehicle listings with filters including make, model, year, country, state, etc. Returns paginated results with lot summaries.
| Param | Type | Description |
|---|---|---|
| make | string | Vehicle make (e.g., toyota, honda, ford) |
| page | integer | Page number |
| size | integer | Results per page |
| sort | string | Sort field |
| model | string | Vehicle model (e.g., camry, civic) |
| order | string | Sort order: asc, desc |
| query | string | Free text search query |
| state | string | State filter (e.g., california, texas) |
| country | string | Country filter (e.g., usa, canada) |
{
"type": "object",
"fields": {
"lots": "array of vehicle listing summary objects",
"query": "object containing pagination metadata (page, size, start, maxNumberOfPages)",
"total": "integer total number of matching results"
},
"sample": {
"data": {
"lots": [
{
"make": "Toyota",
"sold": false,
"year": 2023,
"model": "Tundra",
"highBid": 13500,
"currency": "USD",
"saleDate": "2026-05-07T00:00:00-07:00",
"lotNumber": 50839356,
"description": "2023 Toyota Tundra Sr5",
"locationName": "WV - Charleston",
"primaryDamage": "Side"
}
],
"query": {
"page": 1,
"size": 3,
"start": 0,
"maxNumberOfPages": 3333
},
"total": 17968
},
"status": "success"
}
}About the autobidmaster.com API
The AutoBidMaster API exposes 9 endpoints covering Copart auction inventory available on AutoBidMaster, from paginated vehicle search to full lot-level detail. Use search_vehicles to filter by make, model, year, state, and free-text query, or call get_vehicle_details with a lot number to retrieve images, damage descriptions, VIN, sale status, and yard location for a specific listing.
Search and Filter Inventory
search_vehicles is the primary discovery endpoint. It accepts optional parameters including make, model, state, query, sort, order, page, and size. Responses return a lots array of vehicle summaries alongside a query object that carries pagination metadata (page, size, start, maxNumberOfPages) and a total integer reflecting the full result count. This makes it straightforward to build paginated browsing or implement a search interface.
Lot-Level Detail
get_vehicle_details accepts a lot_number (sourced from search_vehicles results) and an auction parameter — currently only 'copart' returns results. The lot object in the response includes make, model, year, VIN, images, primary and secondary damage, sale information, and physical yard location. If the lot has been sold, removed, or belongs to a different auction source, the endpoint returns a stale_input response with kind 'input_not_found' rather than an error, so callers can detect stale lot numbers cleanly.
Filter Reference Endpoints
Four enumeration endpoints — get_popular_makes, get_vehicle_types, get_body_styles, and get_damage_types — each return arrays of objects with key, label, and cnt fields. The cnt field is the current listing count, making these useful for building faceted-search UI or understanding inventory distribution across damage categories like Front End, Hail, and Rear End. get_featured_items adds a filterSection field alongside key, label, and cnt, covering categories such as Clean Title, Buy It Now, and Pure Sale Items.
Location and Homepage Inventory
get_auction_locations returns yard/sale locations with listing counts, useful for filtering by geography or displaying regional inventory density. get_homepage_inventory bundles popular makes, featured categories, and vehicle types into a single call — each item includes label, cnt, and link — making it efficient for populating a summary dashboard without multiple round trips.
- Building a saved-search alert system that monitors
search_vehiclesfor new lots matching a buyer's make, model, and state criteria - Aggregating damage-type distribution using
get_damage_typescnt values to analyze Copart inventory condition trends over time - Displaying lot detail pages — images, VIN, damage, and location — by chaining
search_vehiclesresults intoget_vehicle_detailscalls - Populating a faceted search UI with current counts from
get_body_styles,get_vehicle_types, andget_popular_makes - Identifying regional auction supply by querying
get_auction_locationsand correlating location counts with specific makes viasearch_vehicles - Tracking Clean Title and Buy It Now inventory volumes using
get_featured_itemscnt fields - Building a mobile app homepage summary using the single
get_homepage_inventoryresponse instead of calling multiple enumeration endpoints
| 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 AutoBidMaster have an official developer API?+
What does `get_vehicle_details` return if a lot number is no longer active?+
stale_input response with kind set to 'input_not_found' rather than throwing an HTTP error. This lets callers distinguish a missing lot from a network or request failure.Which auction sources are supported by `get_vehicle_details`?+
auction parameter currently only returns results when set to 'copart'. IAAI and other auction sources are not covered at this time. You can fork this API on Parse and revise it to add support for additional auction sources.Can I filter `search_vehicles` results by body style or damage type?+
search_vehicles endpoint currently accepts make, model, state, query, sort, order, page, and size as filter parameters. Body style and damage type are not available as direct search filters, though get_body_styles and get_damage_types return their keys and counts. You can fork this API on Parse and revise it to add those filter parameters to the search endpoint.How fresh is the auction inventory data?+
search_vehicles may already be sold by the time you call get_vehicle_details. The stale_input response on get_vehicle_details is the mechanism for detecting this condition.