Looking for the overview — what this API returns, what it costs, and a call you can run without a key? See the Sauto.cz API page →
docs / sauto

Sauto.cz

Sauto.cz

base /sauto/v13 endpoints
post/sauto/v1/listing1 credit

The full detail document of one Sauto ad: description, condition, body, colour, drivetrain, engine power and displacement, doors, seats, airbags, VIN, roadworthiness (STK) expiry, service book, VAT treatment, the complete equipment list with its categories, and every photo. Takes the numeric id or a sauto.cz detail url. The seller's phone number is never fetched or returned.

ParameterAllowed / rangeDescription
idoptional1–Sauto item id — the number at the end of every detail url, and the `id` of every search hit. Give this or `url`.
urloptional—A sauto.cz detail link; the id is read off the end of it. Give this or `id`.
Try in playground →
post/sauto/v1/filters1 credit

The resolver for `search`: Sauto's own codebooks, per category. With no `filter` it lists every filter that category publishes (name_id + Czech label + whether the search endpoint honours it). With a `filter` it returns that codebook's values — makes, models, body styles, colours, equipment codes — each with the seo slug `search` expects. Needed because the body and model vocabularies are different for cars, motorcycles and trucks.

ParameterAllowed / rangeDescription
category = osobnioptionalosobni · uzitkova · nakladni · motorky · ctyrkolky · privesy-navesy · obytne · pracovni-stroje · autobusyWhich section's codebooks to read.
filteroptional—A filter `name_id` from this action's own no-filter listing, e.g. manufacturer_cb, model_cb, vehicle_body_cb, color_cb, equipment_cb. Omit it to see the list.
makeoptional—Only with filter=model_cb: keep just this manufacturer's models. Sauto has no server-side parent filter, so the full model codebook is read and matched on each value's own parent.
page = 1optional1–1-based page over a codebook's values.
page_size = 200optional1–1000Values per page, 1-1000.
Try in playground →
Built for volume
5M+ requests a day

Measured at 60 requests a second across the fleet, with no central bottleneck. Volume pricing is on request, and per-key limits are raised for high-volume accounts.

Missing a source?
We build it

Tell us a site we do not cover yet and it becomes an engine. A customer asked for bestprice.gr on a Sunday and it was in the catalog the next day.

Support
2 minute median reply

Median time from a question in the live chat to the first answer, measured across every answered conversation. Setup help included, no support tier to buy.

One key, one balance
Every API included

No per-site plans and no separate subscriptions. One key and one credit pool across the whole catalog, so adding a source costs nothing up front.

Planning something large? Tell us the volume and the sources and we will come back with what it costs and what we would have to build.