Crawlora icon

Crawlora

Get structured web data from the public web via the Crawlora API

Actions166

Datasets → Datasets Vehicle Listings Search

AI-generated

Summary

Searches Crawlora’s vehicle listings dataset using text and exact-match filters, price and year bounds, mileage, price-reduction status, and sorting. Sends the selected filters and pagination values as query parameters and requires an API key in the x-api-key header.

Inputs

  • Q — Full-text query over make, model, and trim (up to 256 characters).
  • Source — Marketplace filter: carmax, autotrader, or carsdotcom; defaults to carmax.
  • Make, Model, Trim, Body Style, Transmission, Drive Type, Fuel Type — Exact-match listing filters. The UI documents a 128-character maximum for each; examples include Honda, Civic, Sedan, and Hybrid.
  • Seller Type — Filter by retailer, dealer, or private; defaults to retailer.
  • State — Exact US state abbreviation filter, such as CA (up to 8 characters).
  • Vin — Exact VIN filter; matching is best-effort and is not guaranteed for every listing.
  • Run Id — Exact crawl run ID filter (up to 128 characters).
  • Is Price Reduced — Whether to filter for listings currently marked down from a previous price; defaults to true.
  • Min Year, Max Year — Minimum and maximum model year.
  • Min Price, Max Price — Minimum and maximum price in US dollars.
  • Max Mileage — Maximum odometer mileage.
  • Sort — Sort order: relevance, recently updated, newly listed, price, mileage, or year in ascending or descending order; defaults to relevance.
  • Page — Page number; the UI says it defaults to 1.
  • Page Size — Results per page; the UI says it defaults to 20 and allows up to 100. The product of page and page size must be no greater than 10,000.
  • X Api Key (required) — API key sent in the x-api-key request header.
  • Request Options — Optional HTTP request settings: batching, SSL certificate validation, proxy, and timeout.

Output shape

A response from the Crawlora vehicle listings search endpoint.

The supplied source pack contains node metadata but no request execution or response parsing code, so the response fields and pagination envelope cannot be determined from the source. Numeric query fields have UI defaults of 0, while the property descriptions document the endpoint defaults for page and page size.

Links

Discussion