# Immowelt Search API Documentation

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](/docs/immowelt-api/immowelt_locations) to resolve cities, districts, and postal codes before search. Use [Search Count](/docs/immowelt-api/immowelt_count) when you want to estimate market size before paginating through result sets. Use [Property Details](/docs/immowelt-api/immowelt_property) when a search result needs to be enriched into a single listing record. For broader German real estate coverage, compare the [Immowelt API overview](/apis/immowelt-api) and the [Immobilienscout24 Search API](/docs/immobilienscout24-api/immobilienscout24_search).

- **Documentation:** [https://scrappa.co/docs/immowelt-api/immowelt_search](https://scrappa.co/docs/immowelt-api/immowelt_search)
- **API group:** Immowelt API
- **Endpoint:** `GET https://scrappa.co/api/immowelt/search`

## Authentication

Send your Scrappa API key in the `X-API-KEY` request header. Paid endpoints also support accountless x402 payments when called without an API key.

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `location` | string | Yes | City name, postal code, or location ID (e.g., "Berlin", "10115", "1") |
| `type` | string | No | Property type: apartment-rent, apartment-buy, house-rent, house-buy (default: apartment-rent) |
| `price_min` | integer | No | Minimum price in EUR |
| `price_max` | integer | No | Maximum price in EUR |
| `rooms_min` | number | No | Minimum number of rooms |
| `rooms_max` | number | No | Maximum number of rooms |
| `size_min` | integer | No | Minimum size in m^2 |
| `size_max` | integer | No | Maximum size in m^2 |
| `page` | integer | No | Page number for pagination |
| `per_page` | integer | No | Number of results per page (max: 50, default: 20) |

## Example request

```bash
#!/bin/bash

curl -X GET \
    -H "x-api-key: YOUR_API_KEY_HERE" \
    "https://scrappa.co/api/immowelt/search?location=Berlin&type=apartment-rent"
```

## Example response

```json
{
    "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"
        }
    ]
}
```

## Frequently asked questions

### 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.

## Related endpoints

- [Location Autocomplete](https://scrappa.co/docs/immowelt-api/immowelt_locations)
- [Property Details](https://scrappa.co/docs/immowelt-api/immowelt_property)
- [Search Count](https://scrappa.co/docs/immowelt-api/immowelt_count)

## More Scrappa resources

- [API documentation](https://scrappa.co/docs)
- [Full LLM-readable API reference](https://scrappa.co/llms-full.txt)
- [OpenAPI specification](https://scrappa.co/docs/api.json)
- [Pricing](https://scrappa.co/pricing)