Auto.dev

Vehicle Listings API

Access millions of active vehicle listings with real-time pricing and availability

Get comprehensive vehicle listings from U.S. physical & online dealers in seconds. Our Vehicle Listings API provides detailed vehicle information, dealership data, specifications, and market pricing.

Endpoint

GET https://api.auto.dev/listings
GET https://api.auto.dev/listings/{vin}

Returns vehicle listings. Without a VIN, returns an array of listings (typically 100 per page). With a VIN, returns a single specific listing.

View in Browser

https://api.auto.dev/listings

Parameters

PropTypeDefault
vin?
string
-

Pagination

Pagination is supported for large result sets.

Use the page parameter to navigate through the results. For example, page=2 will return the second page of results.

Limit the number of results per page using the limit parameter. For example, limit=10 will return 10 results per page.

PropTypeDefault
page?
number
1
limit?
number
100
https://api.auto.dev/listings?page=2&limit=50

Location Filtering

Filter listings by geographic location using the zip and distance parameters.

PropTypeDefault
zip?
string
-
distance?
number
50
https://api.auto.dev/listings?zip=33132&distance=50

Search Listings

Simply make a GET request to listings with your desired search parameters. You can filter by make, model, year, price, mileage, and more. Add .not to the end of the parameter name to exclude values. Use commas to specify multiple values.

https://api.auto.dev/listings?vehicle.make=ford&vehicle.model=mustang
https://api.auto.dev/listings?vehicle.fuel.not=*gas*,diesel

For example, to find Toyota Camrys under $30k in California:

https://api.auto.dev/listings?vehicle.make=Toyota&vehicle.model=Camry&retailListing.price=1-30000&retailListing.state=CA

Example Request

curl -X GET "https://api.auto.dev/listings/10ARJYBS7RC154562" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"

Response Structure

Single Listing Object Structure

Both endpoints return listing objects with the same structure, but wrapped differently:

  • /listings wraps them in: {data: [array of listing objects]}
  • /listings/{vin} wraps them in: {data: {single listing object}}

Each listing object contains:

Example Responses

Error Responses

Invalid Parameter

{
  "status": 400,
  "error": "Invalid parameter provided: make. This parameter does not exist in this endpoint.",
  "code": "INVALID_PARAMETER",
  "path": "/listings",
  "requestId": "966e8386bb38f095"
}

Invalid VIN

{
  "status": 400,
  "error": "Invalid VIN format: \"123INVALID\" - VIN must be exactly 17 characters",
  "code": "INVALID_VIN_FORMAT",
  "path": "/listings/123INVALID",
  "requestId": "a1b2c3d4e5f6g7h8"
}

VIN Not Found

{
  "status": 404,
  "error": "Resource \"WP0AF2A99KS165242\" not found",
  "code": "RESOURCE_NOT_FOUND",
  "path": "/listings/WP0AF2A99KS165242",
  "requestId": "966716ac29ed8147"
}

Interactive API Reference

Ready to test these endpoints? Use our interactive API playground to make live requests and see real responses.

Plan Availability

  • Starter: ✅ Available
  • Growth: ✅ Available
  • Scale: ✅ Available

See pricing for plan details and signup.

Was this API reference helpful?