Hasznaltauto APIhasznaltauto.hu ↗
Access used car listings and detailed specifications from Hasznaltauto.hu, Hungary's largest second-hand car marketplace, via a simple REST API.
What is the Hasznaltauto API?
The Hasznaltauto.hu API provides access to Hungary's largest used car marketplace through 2 endpoints, returning listing data and full vehicle specifications. The list_cars endpoint retrieves paginated batches of 75 cars per page including name, price, and URL, while car_details returns granular technical specs, seller name, and location for any individual listing.
curl -X GET 'https://api.parse.bot/scraper/bcb94485-054e-4b0f-9fa5-bc9d135a14eb/list_cars?page=1' \ -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 hasznaltauto-hu-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.
"""Walkthrough: Hasznaltauto.hu SDK — browse Hungarian used car listings."""
from parse_apis.hasznaltauto_hu_car_scraper_api import Hasznaltauto, CarNotFound
client = Hasznaltauto()
# List the first few car summaries available on hasznaltauto.hu
for car in client.carsummaries.list(limit=5):
print(car.name, car.price)
# Drill into the first listing's full details
car_summary = client.carsummaries.list(limit=1).first()
if car_summary:
detail = car_summary.details()
print(detail.title, detail.price, detail.seller, detail.location)
# Handle a missing listing gracefully
try:
bad_summary = client.carsummaries.list(limit=1).first()
if bad_summary:
info = bad_summary.details()
print(info.title, info.price)
except CarNotFound as exc:
print(f"Listing gone: {exc.url}")
print("exercised: carsummaries.list / car_summary.details / CarNotFound catch")
List used cars (személyautó) currently available on hasznaltauto.hu. Returns paginated results ordered by the site's default sort. Each page contains up to ~100 car summaries. Pagination advances by integer page number; the site does not expose total page count so iteration stops when a page returns fewer items than expected.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-based). |
{
"type": "object",
"fields": {
"cars": "array of car listing objects, each with name (string), url (string), price (string), and attributes (array of strings such as fuel type, year, engine displacement)",
"page": "integer, the current page number",
"total_on_page": "integer, number of cars returned on this page"
},
"sample": {
"data": {
"cars": [
{
"url": "https://www.hasznaltauto.hu/szemelyauto/peugeot/rifter/peugeot_rifter_1.2_puretech_allure_ss_l1_kizarolag_gyartasrendelesbol_elerheto_modell-20789545",
"name": "PEUGEOT RIFTER 1.2 PureTech Allure S&S L1",
"price": "10 855 000 Ft",
"attributes": [
"Benzin",
"2024",
"1 199 cm³"
]
}
],
"page": 1,
"total_on_page": 95
},
"status": "success"
}
}About the Hasznaltauto API
Endpoints Overview
The API exposes two endpoints. list_cars returns paginated results from Hasznaltauto.hu's inventory of személyautó (passenger car) listings. Each page delivers up to 75 car objects, each containing the car's name, url, price, and a set of listing attributes. The page parameter (1-based integer) controls pagination, and the response includes total_on_page so you can detect partial pages at the end of the result set.
Car Details
Passing any listing URL from Hasznaltauto.hu to car_details returns a richer object. Fixed fields include title, price (formatted as a Hungarian Forint string, e.g. 10 855 000 Ft), seller, and location. Beyond those, the response contains dynamic specification keys in Hungarian — fields such as Kategória (category), Szélesség (width), and other technical attributes that vary by vehicle. This means the exact set of keys in the response depends on what the individual seller has filled in for that listing.
Data Shape and Coverage
Because the dynamic specification keys are in Hungarian and vary per listing, consuming code should handle missing keys gracefully. The url field returned by list_cars is directly usable as the url input to car_details, making it straightforward to chain the two endpoints for bulk data collection. Coverage is limited to passenger cars (személyautó); other vehicle categories listed on the site are not currently in scope.
Source Context
Hashnaltauto.hu is Hungary's primary online marketplace for used vehicles. It does not publish an official public developer API. This Parse API is the practical way to integrate its listing data into external applications.
The Hasznaltauto API is a managed, monitored endpoint for hasznaltauto.hu — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hasznaltauto.hu 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 hasznaltauto.hu 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?+
- Track price trends for specific makes and models across the Hungarian used car market using
list_carsandpricefields. - Build a vehicle comparison tool by pulling full specs from
car_detailsfor multiple listings. - Monitor new listings as they appear by paginating
list_carsand detecting new URLs over time. - Aggregate seller and location data from
car_detailsto map dealership density across Hungarian regions. - Feed listing data into a price estimation model by combining
attributesfromlist_carswith technical specs fromcar_details. - Populate an internal inventory database with structured car data including title, price, and specifications.
| 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 Hasznaltauto.hu have an official public developer API?+
What does `car_details` return beyond price and title?+
car_details returns seller (the dealer or private seller name), location (the seller's address or region), and a variable set of Hungarian-language specification keys such as Kategória and Szélesség. The exact keys depend on what the individual listing includes, so not all vehicles will have the same set of fields.Can I filter `list_cars` results by make, model, price range, or year?+
list_cars endpoint currently accepts only a page parameter for pagination and returns all available listings without filter options. You can fork this API on Parse and revise it to add filter parameters targeting specific makes, models, or price ranges.Does the API cover vehicle categories other than passenger cars?+
How fresh is the listing data, and are removed listings handled?+
car_details with its URL will return an error or empty response rather than cached data. Building in error handling for missing listings is advisable when processing results in bulk.