Immowelt Search API Documentation
Immowelt Search API documentation
Endpoint documentation for searching Immowelt property listings as JSON
This page targets developers looking for Immowelt Search API documentation, an API for Immowelt.de, or an alternative to building an Immowelt scraping workflow from scratch. Start with location resolution, run listing searches with filters, then fetch details for records that matter.
Scrappa's GET /api/immowelt/search endpoint is the Immowelt Search API documentation page for developers who need Immowelt.de property listings as structured JSON instead of building their own scraper.
Endpoint reference for Immowelt.de property search
Use this endpoint to search apartments and houses for rent or sale across Germany. The request supports location, listing type, price ranges, room filters, size filters, page, and per_page, which makes it suitable for search interfaces, market monitoring, lead generation, rental alerting systems, and German real estate data products that need repeatable result feeds.
What the Immowelt search response returns
Each response includes listing IDs, online IDs, listing titles, prices, room counts, square meter values, address text, coordinates, image URLs, listing URLs, publish timestamps, and pagination fields such as total_results, page, and total_pages. That gives you a search-ready listing feed instead of raw HTML that still needs parsing.
How this differs from an Immowelt scraper build
If you are evaluating how to scrape Immowelt.de, this endpoint replaces the brittle search step with one documented API call. Scrappa handles request routing, extraction, and normalization so your application can focus on query logic and downstream analysis rather than browser automation, proxy rotation, or parser upkeep.
Immowelt search API use cases
Use the search endpoint as the first step in workflows that need fresh German property supply data. Rental analytics teams can query Berlin, Munich, Hamburg, Cologne, and Frankfurt with consistent room, size, and price filters to compare availability by city or district. Proptech products can run saved searches for renters and buyers, then trigger alerts when new listings match a budget, room count, or square meter range. Real estate investors can combine paginated search results with listing details to screen neighborhoods, compare yield assumptions, and monitor asking-price changes over time.
For cross-portal coverage, query Immowelt search beside ImmobilienScout24 or other real estate APIs and deduplicate by address, coordinates, listing URL, and price. This gives applications a broader view of the German housing market than a single portal search page can provide.
When to pair this endpoint with the other Immowelt docs
Use Location Autocomplete to resolve cities, districts, and postal codes before search. Use Search Count when you want to estimate market size before paginating through result sets. Use Property Details when a search result needs to be enriched into a single listing record. For broader German real estate coverage, compare the Immowelt API overview and the Immobilienscout24 Search API.
Implementation playbook
What teams build with this endpoint
Rental market dashboards
Run recurring Immowelt searches for major German cities, normalize price, rooms, size, and address fields, and chart availability or asking rent trends by location.
Saved-search alerts
Power renter or buyer alerts by querying location, price, rooms, and size filters on a schedule, then sending notifications when matching listings appear.
Cross-portal property coverage
Combine Immowelt search results with ImmobilienScout24 data, then deduplicate by coordinates, address text, price, and listing URLs for broader German market coverage.
Run this endpoint
Endpoint
https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent
https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent
x-api-key
location
= Berlin
{
"success": true,
"total_results": 1234,
"page": 1,
"total_pages": 62,
"results": [
{
"id": "estate_abc123",
"online_id": "2kub55g",
"title": "Sample listing in Berlin",
"price": 2440,
"price_formatted": "2.440 EUR",
"rooms": 4,
"rooms_max": null,
...
Parameters
Start with the required fields, then add optional filters only when your use case needs them.
Runnable path
1 required parameter needed before sending a request.
9 optional filters available.
string
Required
City name, postal code, or location ID (e.g., "Berlin", "10115", "1")
Berlin
string
Optional
Property type: apartment-rent, apartment-buy, house-rent, house-buy (default: apartment-rent)
apartment-rent
integer
Optional
Minimum price in EUR
10
integer
Optional
Maximum price in EUR
10
number
Optional
Minimum number of rooms
10
number
Optional
Maximum number of rooms
10
integer
Optional
Minimum size in m^2
10
integer
Optional
Maximum size in m^2
10
integer
Optional
Page number for pagination
1
integer
Optional
Number of results per page (max: 50, default: 20)
10
Request Examples
<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 30,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "GET",
CURLOPT_HTTPHEADER => [
"x-api-key: YOUR_API_KEY_HERE"
],
]);
$response = curl_exec($curl);
$err = curl_error($curl);
curl_close($curl);
if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
}
<?php
use Illuminate\Support\Facades\Http;
$response = Http::timeout(30)
->withHeaders(['x-api-key' => 'YOUR_API_KEY_HERE'])
->get('https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent');
if ($response->successful()) {
echo $response->body();
} else {
echo "Error: " . $response->status();
}
const options = {
method: 'GET',
headers: {
'x-api-key': 'YOUR_API_KEY_HERE'
}
};
fetch('https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent', options)
.then(response => {
if (!response.ok) {
throw new Error(`HTTP error! status: ${response.status}`);
}
return response.text();
})
.then(data => console.log(data))
.catch(error => console.error('Error:', error));
const axios = require('axios');
const options = {
method: 'GET',
url: 'https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent',
headers: {
x-api-key: 'YOUR_API_KEY_HERE',
}
};
try {
const response = await axios(options);
console.log(response.data);
} catch (error) {
console.error('Error:', error.message);
}
require 'net/http'
require 'uri'
uri = URI.parse("https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent")
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = uri.scheme == 'https'
request = Net::HTTP::Get.new(uri.request_uri)
request['x-api-key'] = 'YOUR_API_KEY_HERE'
begin
response = http.request(request)
puts response.body
rescue => e
puts "Error: #{e.message}"
end
import http.client
import json
conn = http.client.HTTPSConnection("scrappa.co")
headers = {
'x-api-key': 'YOUR_API_KEY_HERE',
}
try:
conn.request("GET", "/api/immowelt/search?location=Berlin&type=apartment-rent", headers=headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))
except Exception as e:
print(f"Error: {e}")
finally:
conn.close()
import requests
headers = {
'x-api-key': 'YOUR_API_KEY_HERE',
}
try:
response = requests.get('https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent', headers=headers)
response.raise_for_status()
print(response.text)
except requests.exceptions.RequestException as e:
print(f"Error: {e}")
import okhttp3.OkHttpClient;
import okhttp3.Request;
import okhttp3.Response;
import java.io.IOException;
public class ApiExample {
public static void main(String[] args) {
OkHttpClient client = new OkHttpClient();
Request request = new Request.Builder()
.url("https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent")
.addHeader("x-api-key", "YOUR_API_KEY_HERE")
.build();
try (Response response = client.newCall(request).execute()) {
if (response.isSuccessful()) {
System.out.println(response.body().string());
} else {
System.out.println("Error: " + response.code());
}
} catch (IOException e) {
System.out.println("Error: " + e.getMessage());
}
}
}
package main
import (
"fmt"
"net/http"
"io/ioutil"
)
func main() {
client := &http.Client{}
req, err := http.NewRequest("GET", "https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent", nil)
if err != nil {
fmt.Println("Error creating request:", err)
return
}
req.Header.Set("x-api-key", "YOUR_API_KEY_HERE")
resp, err := client.Do(req)
if err != nil {
fmt.Println("Error making request:", err)
return
}
defer resp.Body.Close()
body, err := ioutil.ReadAll(resp.Body)
if err != nil {
fmt.Println("Error reading response:", err)
return
}
fmt.Println(string(body))
}
#!/bin/bash
curl -X GET \
-H "x-api-key: YOUR_API_KEY_HERE" \
"https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent"
using System;
using System.Net.Http;
using System.Threading.Tasks;
class Program
{
static async Task Main()
{
using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY_HERE");
try
{
var response = await client.SendAsync(new HttpRequestMessage(HttpMethod.Get, "https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent"));
var content = await response.Content.ReadAsStringAsync();
Console.WriteLine(content);
}
catch (Exception ex)
{
Console.WriteLine($"Error: {ex.Message}");
}
}
}
import axios from 'axios';
async function run(): Promise<void> {
try {
const response = await axios({
method: 'GET',
url: 'https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent',
headers: {
'x-api-key': 'YOUR_API_KEY_HERE',
},
});
console.log(response.data);
} catch (error) {
console.error('Error:', error);
}
}
void run();
use reqwest::Client;
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let client = Client::new();
let response = client
.get("https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent")
.header("x-api-key", "YOUR_API_KEY_HERE")
.send()
.await?;
println!("{}", response.text().await?);
Ok(())
}
Response Schema
{
"success": true,
"total_results": 1234,
"page": 1,
"total_pages": 62,
"results": [
{
"id": "estate_abc123",
"online_id": "2kub55g",
"title": "Sample listing in Berlin",
"price": 2440,
"price_formatted": "2.440 EUR",
"rooms": 4,
"rooms_max": null,
"size_m2": 137,
"size_m2_max": null,
"address": "Berlin, Germany",
"lat": 52.52,
"lon": 13.405,
"image_url": "https://pictures.immowelt.de/sample.jpg",
"url": "https://www.immowelt.de/expose/2kub55g",
"is_private": false,
"published": "2024-01-15T10:00:00Z"
}
]
}
Generate Code with AI
Copy a ready-made prompt with all the endpoint details, parameters, and example responses. Paste it into ChatGPT, Claude, or any AI assistant to instantly generate working code.
Related Endpoints
Immowelt API FAQ
Answers for developers looking for an API for Immowelt.de and teams evaluating Immowelt scraping workflows.
Is there an official API for Immowelt.de property search?
Immowelt does not offer a public developer API for general property search access. Scrappa provides an API for Immowelt.de that returns listing search results as structured JSON with documented parameters and API key authentication.
How do I call the Immowelt search endpoint?
Send a GET request to /api/immowelt/search with an x-api-key header and at minimum a location parameter. You can then add type, price_min, price_max, rooms_min, rooms_max, size_min, size_max, page, and per_page to narrow the result set.
How can I scrape Immowelt.de without building my own scraper?
Use this endpoint instead of maintaining a custom Immowelt scraper. Scrappa handles the extraction layer and returns normalized JSON, so your app can call one API endpoint for listing search rather than managing browsers, parsers, or proxy rotation.
What data does the Immowelt search API return?
The response includes listing IDs, online IDs, titles, price fields, room counts, size, address text, latitude and longitude, image URLs, listing URLs, publication timestamps, and pagination metadata such as total_results and total_pages.
When should I use search, count, or property details?
Use the search endpoint when you need listing result pages, the count endpoint when you need market size without pagination, and the property details endpoint when you want to enrich one listing returned from search. Together they cover discovery, sizing, and detail retrieval workflows.