Chileautos APIchileautos.cl ↗
Search car listings, retrieve vehicle details, and get brand lists from chileautos.cl, Chile's largest auto marketplace. 3 endpoints, full specs included.
What is the Chileautos API?
The chileautos.cl API provides 3 endpoints to access car listings and vehicle data from Chile's largest automotive marketplace. Use search_listings to filter by brand, model, or page, get_listing_detail to pull full specs on a specific vehicle by its network ID, and get_brands to retrieve the complete list of makes — from Abarth to Zongshen — with the filter values needed for search queries.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/a82ccf0c-e786-4718-8b13-701418ac542c/get_brands' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace chileautos-cl-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""
Search car listings on chileautos.cl and retrieve vehicle details.
"""
from parse_apis.chileautos_api import Chileautos, Brand, Listing, ListingDetail
client = Chileautos()
# List available brands
for brand in client.brands.list(limit=5):
print(brand.name, brand.value)
# Search Toyota listings
for listing in client.listings.search(brand="Toyota", limit=3):
print(listing.title, listing.price, listing.year, listing.location)
# Get full details for each listing
detail = listing.details()
print(detail.listing_id, detail.summary, detail.details)
Retrieve the full list of car brands available on chileautos.cl. Returns brand names and their corresponding filter values for use in search_listings. The list is exhaustive and includes all makes from Abarth to Zongshen.
No input parameters required.
{
"type": "object",
"fields": {
"brands": "array of brand objects each with 'name' (display name) and 'value' (filter value like 'Marca.Toyota.')"
},
"sample": {
"data": {
"brands": [
{
"name": "Abarth",
"value": "Marca.Abarth."
},
{
"name": "Toyota",
"value": "Marca.Toyota."
},
{
"name": "BMW",
"value": "Marca.BMW."
}
]
},
"status": "success"
}
}About the Chileautos API
Endpoints and Data Coverage
The API exposes three endpoints. get_brands returns a flat array of brand objects, each with a name (display label) and value (the filter string, e.g. Marca.Toyota.) ready to pass directly into search_listings. The brand list is exhaustive and covers all makes listed on chileautos.cl at the time of the request.
Searching Listings
search_listings accepts optional brand, model, and page parameters. Brand and model values are automatically formatted into the required filter syntax, so passing Toyota or Marca.Toyota. both work. Results return up to 26 listing objects per page, each containing id, title, price, year, location, make, model, and url. Note that results include sponsored and promoted placements alongside organic listings. A current_page field confirms pagination state. For advanced filtering, the query parameter accepts a raw DSL string when brand/model params are not used.
Vehicle Detail
get_listing_detail takes a listing_id (e.g. CP-AD-8522747) sourced from search_listings results and returns two objects. The summary object contains high-level metadata: make, model, year, price, condition, fueltype, bodystyle, colour, state, and genericgeartype. The details object provides specification key-value pairs such as Transmisión, Puertas, Versión, Región, and Comuna. An optional slug parameter is accepted but does not affect the data returned.
The Chileautos API is a managed, monitored endpoint for chileautos.cl — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when chileautos.cl changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official chileautos.cl API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a price comparison tool for used cars in Chile using
price,make,model, andyearfromsearch_listings. - Aggregate regional inventory by filtering
search_listingsresults by brand and extractinglocationfields. - Populate an auto-classifier with transmission, fuel type, and body style data from
get_listing_detail. - Monitor listing availability for a specific make/model by paginating
search_listingsand trackingidchanges over time. - Generate a structured brand catalog from
get_brandsto build dropdown filters in a vehicle search UI. - Extract commune and region data from
get_listing_detailto map vehicle inventory distribution across Chile. - Track seller type patterns across listings by reading the
sellertypefield in thesummaryobject.
| 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 | 100 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 chileautos.cl have an official developer API?+
What does `get_listing_detail` return beyond what appears in search results?+
search_listings returns summary fields like price, year, make, and model. get_listing_detail adds a details object with spec-level fields — Transmisión, Puertas, Versión, Color exterior, Región, and Comuna — plus a summary object with condition, fueltype, bodystyle, colour, state, genericgeartype, and sellertype. You need the listing_id from search results to call it.Does `search_listings` return only organic results, or are sponsored listings included?+
Can I filter listings by price range, year, or fuel type?+
search_listings endpoint currently supports filtering by brand, model, and page, plus a raw query DSL string for advanced cases. Dedicated parameters for price range, year, or fuel type are not exposed. You can fork this API on Parse and revise it to add those filter parameters if the underlying query DSL supports them.