LUNTERO FOR DEVELOPERS
Build rental search, relocation tools and housing dashboards with structured Netherlands listings, location data and the resources people need before and after a move.
JSON responses. OpenAPI contract. Interactive examples.
/v1/listingscurl 'https://api.luntero.com/v1/listings?limit=5' \
-H "Authorization: Bearer $LUNTERO_API_KEY"THE DATA BEHIND YOUR IDEAS
Finding a rental is only one part of moving. Luntero brings property discovery, information about places and practical housing resources into one JSON API, so your product can support more of that journey. Start with a single dataset or combine several through their returned IDs.
Filter published rentals by location, monthly rent, size, rooms and furnishing. Retrieve descriptions, images and source links, find similar homes, or get statistics for a search.
/v1/listingsFind location records and localized place names, then connect them with listing searches. Retrieve public owner and agency profiles to give users more context about a rental.
/v1/locationsExplore average and median rent, rent per square metre, median property size and new-listing volume. Request monthly observations for a city to build charts around advertised supply.
/v1/market/metricsHelp readers navigate Dutch housing with published articles, handbooks and their chapters, glossary definitions and rental platform profiles. Request existing translated content where available.
/v1/articlesSearch provider directories separately from internet plans and insurance products. Filter products by provider, inspect stored terms and pricing, and follow source and verification information.
/v1/internet/providersRetrieve stored verified energy labels by exact address, or explore monitoring stations and recorded air-quality measurements. Use the returned dates and units to explain what each result represents.
/v1/energy-labelsWHAT YOU CAN BUILD
Build a property browser that filters homes by budget, size and location. Add listing details, owner profiles and similar properties so a user can move from a broad search to a shortlist without switching between unrelated data formats.
Explore listing searchBring housing guides, rental terminology and provider information into a relocation app. Connect the search for a home with explanations of unfamiliar concepts, internet plans and insurance products people may want to research as they settle in.
Explore housing handbooksUse filtered listing statistics for a view of current published rentals, then add monthly market observations for historical context. Show rent and size trends alongside new-listing volume, with clear labels for the city, period and available sample.
Explore market indicatorsFROM REQUEST TO PRODUCT
Use HTTPS and a Bearer key to request JSON from versioned /v1 endpoints. Listing and resource collections support cursor pagination; each endpoint documents its own filters, response fields and error codes.
The API reference is generated from the Hono OpenAPI contract. Inspect schemas in the browser, try an endpoint with your own key, or download the specification for your tooling. A public ping endpoint lets you test connectivity before requesting any data.
Download OpenAPIContact Luntero to request a key. Read the authentication guide for the current access process and request limits.
Search the locations endpoint, take a returned ID and use it to filter listings alongside rent, size or furnishing.
Use a listing ID to request its full record. Add owner information, similar rentals or relevant housing resources to your experience.
Pass the returned cursor with the same filters. Follow rate-limit headers and use the documented error and retry conventions.
ONE INTEGRATION, DIFFERENT READERS
Add locale=nl, de, fr or es to request existing translations of free-text fields. Missing translations fall back to English. IDs, slugs, prices and structured values stay consistent, while location display names follow the requested language.
Same record. Selected language.
GET /v1/listings/{id}
Authorization: Bearer YOUR_API_KEY
GET /v1/listings/{id}?locale=nl
Authorization: Bearer YOUR_API_KEYKNOW WHAT YOU ARE BUILDING ON
Listing search includes active, published rentals. Market observations describe advertised supply grouped by first-seen month; they do not represent signed contracts or every home in a city. Historical availability depends on stored coverage and minimum sample sizes.
Provider records and resource content have their own publication and verification information. Air-quality results are recorded observations, and energy-label lookups use registrations already stored by Luntero. Use source links, timestamps and validity fields where provided to give your users the right context.
BEFORE YOU INTEGRATE
Yes. The listings endpoints let you search published Dutch rentals, retrieve a property by ID, find similar listings and request filtered search statistics. The API also exposes locations, public owner and agency profiles, editorial housing resources and other datasets described in the reference.
Any client that can make HTTPS requests and read JSON can call the API. For a public website or distributed mobile app, keep a shared API secret on your backend and call Luntero from there. Do not embed a secret key in a public bundle or app binary.
The market endpoints provide monthly observations for supported metrics over a range of up to 24 months, where coverage and sample thresholds allow. These describe advertised rental supply. They are separate from listing search, which returns currently active, published rental records.
No. Available fields depend on the underlying record; unknown values are returned as null. English is the default language, and available translations can be requested with the locale parameter. Missing translated fields fall back to English rather than generating new text.
Contact Luntero to request API access; self-service signup and billing are not available in this release. Start with the authentication guide. Once you have a key, use the endpoint playgrounds or the curl examples. The public ping endpoint works without a key.
Authentication, pagination, language options and error handling.
Read the guidesEndpoint parameters, response schemas and a playground to try them.
Browse the reference