ingatlan.com APIingatlan.com ↗
Search and retrieve real estate listings and development projects from ingatlan.com, Hungary's largest property portal. Get prices, sizes, rooms, and features.
curl -X GET 'https://api.parse.bot/scraper/4d45a3e8-ac62-4a2f-87c8-883c3f88c583/search_listings?query=budapest' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for real estate listings on ingatlan.com. Returns up to 20 listings per request with price, address, size, and room count.
| Param | Type | Description |
|---|---|---|
| query | string | Search query, typically a city or district name. |
| property_type | string | Property type expression used in the URL path. Examples: 'elado+lakas' (apartments for sale), 'kiado+lakas' (apartments for rent). |
{
"type": "object",
"fields": {
"total": "integer count of listings returned",
"listings": "array of listing objects with id, price, address, size, rooms, url"
},
"sample": {
"data": {
"total": 20,
"listings": [
{
"id": "35216902",
"url": "https://ingatlan.com/35216902",
"size": "66 m2",
"price": "149 M Ft",
"rooms": "3",
"address": "Budapest VIII. kerület, Corvin sétány 5."
}
]
},
"status": "success"
}
}About the ingatlan.com API
The ingatlan.com API provides access to Hungarian real estate data through 3 endpoints covering property search, listing details, and new development projects. The search_listings endpoint returns up to 20 results per request with price, address, size, and room count. The get_listing_details endpoint adds year built, a full features table in Hungarian, and a free-text description for any listing ID obtained from search results.
What the API Returns
The search_listings endpoint accepts a query parameter (typically a city or district name) and a property_type string that maps to ingatlan.com URL path expressions — for example elado+lakas for apartments for sale or kiado+lakas for rentals. Each result in the listings array carries an id, price, address, size, rooms, and a direct url. The total field reflects how many listings were returned in that response (up to 20).
Listing Detail Fields
get_listing_details takes a numeric listing_id — obtainable from search_listings results — and returns a structured object. Key fields include size (floor area with unit, e.g. 66 m²), price and price_currency (denominated in HUF), rooms, year_built, location (structured address), a title that includes property type and address, and a description string for the full listing text. The features object is a key-value map of property attributes sourced directly from the listing page; keys and values are in Hungarian.
Development Projects
search_projects returns promoted new-build development projects. It accepts an optional property_type filter (e.g. flat) and returns a projects array where each entry includes a title, description, url, and image. This endpoint is suited for tracking newly launched housing developments rather than resale inventory.
Coverage and Scope
All data is scoped to ingatlan.com, which focuses on the Hungarian property market. Prices are in HUF. Feature labels in the features object are in Hungarian, so consuming applications targeting non-Hungarian audiences will need to handle translation. Pagination is limited — search_listings returns a maximum of 20 listings per call, so broad market surveys require iterating over multiple queries.
- Build a Budapest apartment price tracker using
search_listingswith district-level queries and the returnedpricefield. - Aggregate listing details at scale by chaining
search_listingsIDs intoget_listing_detailsto collectyear_builtandfeaturesdata. - Monitor new housing developments in a target city using
search_projectswith aproperty_typefilter. - Compare rental vs. sale prices by running
search_listingswithkiado+lakasandelado+lakasproperty type expressions. - Extract floor area and room count distributions across a district to produce summary statistics from the
sizeandroomsfields. - Surface listing descriptions via the
descriptionfield inget_listing_detailsfor natural language analysis or translation pipelines.
| 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 | 250 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 ingatlan.com offer an official developer API?+
What does `get_listing_details` return beyond what `search_listings` already provides?+
search_listings returns a summary row: id, price, address, size, rooms, and url. get_listing_details adds year_built, a description text block, price_currency, a structured location field, and a features key-value object containing all additional property attributes shown on the listing page (in Hungarian).Are photo URLs or floor plan images returned by any endpoint?+
search_projects does return a project image field. You can fork this API on Parse and revise it to add image extraction for individual listings.How many results can `search_listings` return per request?+
search_listings returns up to 20 listings per request. There is no built-in pagination parameter exposed in this API. To cover more of the result set for a given query, you can fork the API on Parse and revise it to add a page offset parameter.Are listings outside Hungary covered?+
query and property_type inputs are interpreted in the context of Hungarian cities, districts, and ingatlan.com URL conventions.