Germany Property Listings API - Rent, Buy, Commercial

Pull the German and Austrian listings market into a table: what is on the market, where, at what price, and how many of it a region holds.

What it collects

• Listings by region: search a region code across twenty real estate types, from apartments and houses to flat share rooms, offices, retail stores, gastronomy, industrial space, investment properties, plots and compulsory auctions.
• Listings by radius: the same search around a latitude and longitude with a radius in kilometres.
• One listing in full: the provider assembles the property, its address, its attributes, its contact and its attachments into a single record, so a full listing is one call rather than four.
• Photos, floor plans and videos: every attachment on a listing with its type, title, publication date and file link.
• Places: resolve a town, district, postcode, street or station name to the provider's own region code and coordinates, and walk the hierarchy from continent down to quarter. This is how a place name becomes the code the region search needs.
• Region counts: how many listings a region and its direct subregions hold, broken down by real estate type.
• Mortgage rates: the average nominal and effective interest rates for a region, given a purchase price, own funds, repayment rate, fixed interest period, employment and lender kind.

FAQ

What is a German property listings API used for?

Watching a market rather than browsing it. A portal or a CRM syncs listings into its own product. An analyst tracks asking prices and time on market across districts. A relocation or mortgage service prices a search area before quoting. A valuation model needs live comparables in the same postcode. All of those want the same thing: a repeatable query that returns the market as rows, which is what this actor is.

How do I search a particular area?

By region code or by radius. A region code is the provider's own geocode id, built from continent, country, region, city and quarter ids run together, such as 1276003001014. Run the place lookup service on a name first to get the code, then feed it to the region search. If you already have coordinates, the radius search takes latitude;longitude;radius with the radius in kilometres and skips the lookup entirely. Radius search does not reach properties outside Germany and Austria.

Why does the actor refuse to send some of my filters?

Because this API accepts a different filter set for each real estate type, and its own documentation warns that an unknown search criterion is "ignored or results in an empty result list". The second half of that is the trap: a filter that belongs to another type does not produce an error, it can produce zero hits that look exactly like a market with nothing in it. So the actor keeps each type's documented filters and leaves the rest off the request, and says in the log which ones it dropped and why.

What does an empty price mean?

Price on application, and the row says so. The provider states that it always sends the marketing type, that a missing price means the price is on request, and that on the commercial types and plots a returned price of zero means the same thing. Both cases set priceOnRequest to true rather than leaving an empty column, because "the seller will not say" is a fact about the offer and must not look like a gap in the data.

Can this actor publish a listing or spend money?

No. The provider publishes routes that insert and publish a property, upload attachments, buy on-top placements, create contact requests and book financing appointments, and none of them is wired up anywhere in this actor. Every route it can reach is a read. That is a deliberate limit, because a scheduled run that could put a property on the market is a scheduled run that eventually will.

What credentials do I need, and do I need all of them?

Usually two of the four. This API signs every request with OAuth 1.0a rather than taking a bearer token. Two-legged signing uses your consumer key and consumer secret alone, and that covers the searches, the place services, the region counts and the mortgage rates. Three-legged signing adds an access token and its secret, and is only needed to reach one particular customer's own data, such as their listings on their own homepage channel. The actor runs two-legged when you leave the token blank, and says so in the log.

Why did it say my key was refused without saying what was wrong?

Because the provider does not say either: a refusal is an empty HTTP 401 with no body and no WWW-Authenticate header. Four things produce it, and the actor names all four rather than guessing one: the consumer key or secret is wrong, the machine's clock is too far out for the signed timestamp to verify, the service you chose needs the three-legged access token you left blank, or your account has not been granted permission for that resource. The main portal channel in particular needs a content partner permission on your account.

How do I read only what is new since the last run?

With the first activation filter, which takes a date and time and returns only listings first published after it. The separate published-after field looks similar and does something different: it does not filter at all, it adds a flag to each listing saying whether it was published after that moment. Reaching for the wrong one is how people end up re-reading the whole market every night.

How does paging work?

The search returns the total page count, and the actor walks pages until it reaches it rather than stopping at the first short page, because a page can legitimately come back short of the size you asked for. Page size is yours to set between 1 and 200, and a larger page means fewer requests for the same results. The maximum results input is what bounds the whole run.

Why is the provider's record kept whole instead of split into columns?

Because twenty real estate types answer in twenty shapes, and a fixed set of columns would silently drop most of what you asked for. The columns that are lifted are the ones the provider documents on every entry: the id, the link, the creation and modification timestamps, and the price question above. Everything else sits under record, unchanged, including the whole address and attribute block for that type.

What does it cost?

Pay per result. A listing row costs the most, because it carries the whole property record. A place row costs a little less, an attachment row less again because one listing commonly carries a dozen, and region counts and rate readings are priced near zero, since the readings you take before deciding what to spend on should not themselves cost much. Platform usage is included, and a search that matches nothing is never charged.

Example output

{
  "service": "searchRegion",
  "serviceLabel": "Search listings in a region",
  "realEstateType": "apartmentRent",
  "requested": "1276003001014",
  "found": true,
  "recordType": "listing",
  "id": "123456",
  "listingUrl": "https://rest.immobilienscout24.de/restapi/api/search/v1.0/expose/123456",
  "created": "2026-05-16T20:26:56.000+02:00",
  "modified": "2026-05-17T20:53:24.000+02:00",
  "price": 1450,
  "currency": "EUR",
  "priceOnRequest": false,
  "page": 1,
  "totalHits": 87,
  "record": { "...": "every field the provider published, unchanged" },
  "note": null
}

Keyword map

Germany property API, German real estate API, property listings API Germany, Austria property listings API, apartment rent data Germany, house prices Germany API, commercial real estate API Germany, office listings API, retail property data, German property market data, real estate search API, geocode lookup Germany, postcode lookup Germany, German property portal API, OAuth 1.0a real estate API, Immobilien API, Mietwohnung data feed, property attachments API, floor plan data, mortgage interest rates Germany API, Baufinanzierung rates API, listings by region code, radius property search, compulsory auction listings Germany.