Ohne-Makler Property Search Scraper avatar

Ohne-Makler Property Search Scraper

Pricing

from $0.20 / 1,000 results

Go to Apify Store
Ohne-Makler Property Search Scraper

Ohne-Makler Property Search Scraper

Find German property listings on Ohne-Makler with prices, rooms, area, location, coordinates, and listing links. Batch city searches and page through local results.

Pricing

from $0.20 / 1,000 results

Rating

0.0

(0)

Developer

Scrappa

Scrappa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

Search Ohne-Makler by German city, postal code, county, or state. Collect listing prices, rooms, living area, location, coordinates, and links across result pages.

What data can you extract?

FieldTypeDescription
idIntegerNumeric Ohne-Makler identifier for the property listing.
object_numberStringPublic object number displayed on the Ohne-Makler listing.
titleStringProperty title shown in Ohne-Makler search results.
urlStringPublic Ohne-Makler URL for the property listing.
priceIntegerAdvertised asking price in euros, when the seller publishes it.
price_on_requestBooleanTrue when the seller asks viewers to request the price.
postal_codeStringGerman postal code for the listed property location.
cityStringCity assigned to the listing.
districtString or nullCity district for the property, when reported.
streetString or nullStreet address for the listing, when published.
roomsNumberNumber of rooms advertised for the property.
living_area_m2IntegerAdvertised living area in square metres.
plot_area_m2String or nullLand area in square metres for houses or land listings, when available.
preview_imageStringPreview image URL for the property listing.
seller_typeString or nullSeller category reported by Ohne-Makler, when available.
latitudeNumberProperty latitude in decimal degrees.
longitudeNumberProperty longitude in decimal degrees.
input_qStringQ submitted to retrieve this property listing.
scraped_atStringUTC ISO 8601 timestamp when this dataset record was collected.

Use cases

  • Home seekers can compare listings by location, room count, and living area.
  • Property investors can monitor German supply by city and transaction type.
  • Housing researchers can export asking prices and coordinates for market analysis.

How to use

  1. Add a German place name or postal code to locations for each search.
  2. Choose a property type and buy or rent transaction, then set optional price and area filters.
  3. Set maxPages and maxResults, then export the listing rows.
{
"locations": [
{
"q": "berlin"
}
],
"type": "wohnung",
"transaction": "mieten",
"page": 1,
"maxResults": 5,
"maxPages": 1
}

Input

FieldTypeRequiredDescription
locationsArray<object>YesCity, postal code, county, or state names to resolve on Ohne-Makler.
locations[].qstringYes per entryFree-text location: postal code (80331), city (München), Kreis, or Bundesland. Results are limited to the resolved place (returned as location). State/city segments are not accepted alongside q.
locations[].typestringNoProperty type slug: wohnung, haus, grundstueck, zimmer, buero, einzelhandel, gastronomie, lagerhalle, landwirtschaftliches-objekt, wohnen-auf-zeit, gewerbliche-freizeitimmobilie, zinshaus-rendite, sonstiges, immobilie. Required unless q is used.
locations[].transactionstringNokaufen (buy) or mieten (rent). Required unless q is used.
locations[].statestringNoBundesland URL slug (transliterated umlauts, e.g. baden-wurttemberg). Omit for a Germany-wide class.
locations[].citystringNoCity or Kreis URL slug; requires state.
locations[].pageintegerNo1-based result page. Beyond the last page returns a non-billable 404.
locations[].sortstringNoprice_asc, price_desc, date_asc, or date_desc.
locations[].price_minintegerNoMinimum price in EUR.
locations[].price_maxintegerNoMaximum price in EUR.
locations[].area_minintegerNoMinimum living area in m².
locations[].area_maxintegerNoMaximum living area in m².
locations[].radiusintegerNoUmkreis in km: 0, 10, 25, 50, or 100. Applies when q resolves to a city, or with state + city. Postal codes, Kreise, and states have no Umkreis (non-billable 422 radius_requires_city). Allowed values: 0, 10, 25, 50, 100.
typestringNoProperty type slug: wohnung, haus, grundstueck, zimmer, buero, einzelhandel, gastronomie, lagerhalle, landwirtschaftliches-objekt, wohnen-auf-zeit, gewerbliche-freizeitimmobilie, zinshaus-rendite, sonstiges, immobilie. Required unless q is used.
transactionstringNokaufen (buy) or mieten (rent). Required unless q is used.
statestringNoBundesland URL slug (transliterated umlauts, e.g. baden-wurttemberg). Omit for a Germany-wide class.
citystringNoCity or Kreis URL slug; requires state.
pageintegerNo1-based result page. Beyond the last page returns a non-billable 404.
sortstringNoprice_asc, price_desc, date_asc, or date_desc.
price_minintegerNoMinimum price in EUR.
price_maxintegerNoMaximum price in EUR.
area_minintegerNoMinimum living area in m².
area_maxintegerNoMaximum living area in m².
radiusintegerNoUmkreis in km: 0, 10, 25, 50, or 100. Applies when q resolves to a city, or with state + city. Postal codes, Kreise, and states have no Umkreis (non-billable 422 radius_requires_city). Allowed values: 0, 10, 25, 50, 100.
maxResultsintegerNoMaximum dataset items to save across this entire run.
maxPagesintegerNoMaximum pages to request for each batch entry.

Output example

{
"id": 8000205,
"object_number": "OM-583214",
"title": "Bright two-bedroom flat in Berlin",
"url": "https://www.ohne-makler.net/immobilie/offer/583214/",
"price": 549,
"price_on_request": true,
"postal_code": "10115",
"city": "Berlin",
"district": "Verified source detail",
"street": null,
"rooms": 2,
"living_area_m2": 78,
"plot_area_m2": null,
"preview_image": "https://cdn.northstar.invalid/images/aurora-front.webp",
"seller_type": null,
"latitude": 52.52,
"longitude": 13.405,
"input_q": "berlin",
"scraped_at": "2026-10-01T12:00:00Z"
}

Pricing

$0.30 per 1,000 results. Apify saves one dataset item per result and applies the Actor’s per-result price to saved items.

Pagination follows the source response. Set maxPages per batch entry and maxResults across the run.

FAQ

Rules depend on the source, location, data type, and intended use. Check applicable laws and source terms, and make sure your workflow follows privacy and data protection requirements.

What limits apply?

Submit up to 100 batch entries per run. Use maxResults to cap saved items and maxPages to limit pages for each entry. Results also depend on source availability and your Scrappa API plan.

Can I start runs through the Apify API?

Yes. Send a POST request to https://api.apify.com/v2/acts/thescrappa~ohne-makler-search-scraper/runs with your Actor input, or use an Apify client library. Read the output from the run dataset.

Can I connect the results to other tools?

Yes. Apify integrations and APIs can pass dataset results to Make, Zapier, n8n, Google Sheets, and other data workflows.

What happens when one input fails?

The Actor logs a short source error and continues with the remaining entries. Transient rate limits and gateway errors are retried; if every entry fails, the run reports an error.

Can I search by postal code?

Yes. The location query accepts a city, postal code, county, or German state. A radius filter applies only when the location resolves to a city.