WG-Gesucht Scraper — German Flatshare, WG-Zimmer & Rental Data (No API)

Export German shared-flat and apartment rental listings from WG-Gesucht.de, Germany's #1 portal for a WG room (Wohngemeinschaft / flatshare), a 1-room flat (Wohnung), a whole apartment, a house or a sublet (Zwischenmiete). This scraper turns any WG-Gesucht search into a clean dataset across Berlin, Munich, Hamburg, Cologne, Frankfurt, Leipzig and every German city. No login, no API key, no token.

🏆 Why this WG-Gesucht scraper?

50+ pages / 1,000+ listings per city auto-paginated · rent (€), size (m²), rooms, city, district & street · available-from (+ available-to for sublets) · every URL filter respected · residential-proxy ready · export to JSON / CSV / Excel. The unofficial WG-Gesucht API alternative for rental-price analysis, flatshare market research and availability tracking.

---

✨ What this Actor does / Key features

• 🏠 All categories — WG rooms (flatshares), 1-room flats, whole apartments, houses and sublets (Zwischenmiete).
• 🌍 Every German city — Berlin, Munich, Hamburg, Cologne, Frankfurt, Leipzig and beyond; paste multiple search URLs to cover several cities and categories in one run.
• 💰 Rent & size data — rent in EUR, size in m², room count, plus city, district and street for €/m² analysis.
• 📅 Availability — move-in (availableFrom) date, plus move-out (availableTo) for sublets / Zwischenmiete.
• 👤 Poster context — who posted the ad and how recently they were online.
• 🔗 Filter-aware — every filter you encode in the WG-Gesucht URL (city, price, rooms, move-in date) is respected.
• 📄 Full pagination — the Actor walks the whole result set automatically (often 50+ pages per city).
• ⚡ Server-rendered cards — reads the site's public listing cards; no login and no token.
• 🛡️ Proxy support — Apify Proxy on residential (default) for the highest success rate on this German site.

🚀 Quick start (3 steps)

1. Configure — on WG-Gesucht, pick a city and category, apply your filters, and copy the URL from the address bar into searchUrls (add several for multiple cities/categories).
2. Run — click Start. The Actor paginates every search URL and streams listings into your dataset.
3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API.

📥 Input

Give the Actor at least one searchUrls value. Everything else is optional.

Example — flatshares & apartments across three cities

{
  "searchUrls": [
    "https://www.wg-gesucht.de/wg-zimmer-in-Berlin.8.0.1.0.html",
    "https://www.wg-gesucht.de/wohnungen-in-Muenchen.90.2.1.0.html",
    "https://www.wg-gesucht.de/1-zimmer-wohnungen-in-Hamburg.55.1.1.0.html"
  ],
  "maxResults": 3000
}

Example — WG rooms in Berlin only (deep pagination)

{
  "searchUrls": ["https://www.wg-gesucht.de/wg-zimmer-in-Berlin.8.0.1.0.html"],
  "maxResults": 0
}

Example — capped per-search, multiple cities

{
  "searchUrls": [
    "https://www.wg-gesucht.de/wohnungen-in-Koeln.73.2.1.0.html",
    "https://www.wg-gesucht.de/wohnungen-in-Leipzig.90.2.1.0.html"
  ],
  "maxResultsPerSearch": 500,
  "maxResults": 1000
}

Field	Type	Description
searchUrls	array	WG-Gesucht search-result URLs (copy them straight from the site after applying filters). Each is paginated fully. Required.
maxResults	integer	Global cap across all searches. 0 = no limit.
maxResultsPerSearch	integer	Optional per-search cap.
maxConcurrency	integer	Optional parallelism control.
proxyConfiguration	object	Apify Proxy settings. Residential (the default) is strongly recommended.

Building a search URL: on WG-Gesucht pick a city and category (WG-Zimmer, 1-Zimmer-Wohnung, Wohnung, Haus), apply filters, then copy the URL from the address bar. Add several URLs to scrape multiple cities and categories in one run.

Additional input fields

These optional fields are also available in the input form and API:

Field	Type	Default	Description
rentType	string	"any"	Used only when no Search URLs are given. Long-term or limited/temporary (befristet) rentals.
sortBy	string	"newest"	Used only when no Search URLs are given. How to order the search results.
useProxy	boolean	true	Route requests through Apify Proxy. Residential is recommended and is the default for a German site.

📤 Output

One flat row per listing — exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record:

{
  "id": "13507864",
  "title": "Dachgeschosswohnung 58m² zur Zwischenmiete in Kreuzberg 36",
  "url": "https://www.wg-gesucht.de/wohnungen-in-Berlin-Kreuzberg.13507864.html",
  "listingType": "Apartment",
  "propertyType": "2-Zimmer-Wohnung",
  "rent": 1300,
  "currency": "EUR",
  "sizeSqm": 58,
  "rooms": 2,
  "city": "Berlin",
  "district": "Kreuzberg",
  "street": "Manteuffelstr",
  "availableFrom": "05.06.2026",
  "availableTo": null,
  "posterName": "Herr Müller",
  "onlineStatus": "Online: 2 Minuten",
  "image": "https://img.wg-gesucht.de/media/up/.../thumb.jpg",
  "sourceUrl": "https://www.wg-gesucht.de/wohnungen-in-Berlin.8.2.1.0.html",
  "scrapedAt": "2026-07-06T15:31:24.950Z"
}

💡 Use cases

• Rental-price analysis — track rent, €/m² and room counts across Berlin, Munich, Hamburg and more.
• Flatshare & WG market research — map WG-room supply, districts and availability over time.
• Availability & trend monitoring — schedule daily runs to watch new listings and how fast the market moves.
• Comps & valuation — feed rooms, size, district and rent into pricing or affordability models.
• Portals & dashboards — power a rental feed or BI dashboard straight from the Apify API.
• Relocation & HR — build city-by-city rent snapshots for relocation packages and cost-of-living comparisons.

👥 Who uses it

Proptech & rental-market analysts · relocation & HR teams · data journalists & researchers · rental portals & aggregators · investors & valuation teams · students and expats mapping the market.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the listings you extract, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Do I need a WG-Gesucht account or API key? No. The Actor reads public search-result data — no login and no token. It collects publicly available listing data; you are responsible for complying with WG-Gesucht's terms and your local regulations (including how you use any personal data).

Which categories are supported? All of them — WG rooms (flatshares), 1-room flats, whole apartments, houses and sublets (Zwischenmiete). Just paste that category's search URL into searchUrls.

How do I filter by city, price, rooms or move-in date? Apply the filters on WG-Gesucht itself, then copy the resulting URL. Every filter encoded in the URL is respected, and the Actor paginates the whole result set (often 50+ pages per city).

How many listings can I get per city? A single big-city search (e.g. apartments in Berlin) spans 50+ pages — well over 1,000 listings. Use maxResults to cap the run, or 0 for everything.

Is this a WG-Gesucht API alternative?

Yes. WG-Gesucht has no public API, so this Actor works as a WG-Gesucht API alternative: it reads the public search results directly and gives you the structured listing data an API would, with no token needed.

How do I export WG-Gesucht data to CSV or JSON?

Run the Actor on your search URLs, then download the dataset as CSV, JSON, Excel or XML, or pull it via the Apify API. It's a no-code way to export WG-Gesucht data to CSV without writing a scraper.

Can I scrape WG-Gesucht without login?

Yes. The Actor scrapes WG-Gesucht without login and without an API key, reading only public, server-rendered listing cards across every German city.

How do I scrape WG room (flatshare) listings in Berlin?

On WG-Gesucht pick Berlin and the WG-Zimmer category, apply filters, then paste that search URL into searchUrls; the Actor paginates every flatshare room with rent, size and district.

Can I scrape multiple German cities in one run?

Yes. Add several search URLs for different cities and categories (e.g. Berlin apartments and Munich WG rooms) and the scraper collects them all in a single run.

🔗 More real estate scrapers by logiover

Building a cross-country property dataset? Pair WG-Gesucht with the rest of the European real-estate suite:

Country	Actor
🇩🇪 Germany	ImmobilienScout24 Scraper
🇦🇹 Austria	Willhaben Scraper
🇵🇱 Poland	Otodom.pl Scraper
🇨🇿 Czechia	Sreality.cz Scraper
🇫🇷 France	Bien'ici Scraper
🇮🇹 Italy	Casa.it Scraper · Subito Scraper
🇪🇸 Spain	Habitaclia Scraper · Pisos.com Scraper
🇵🇹 Portugal	Imovirtual Scraper
🇬🇷 Greece	Spitogatos Scraper
🇷🇴 Romania	Storia.ro Scraper
🇮🇪 Ireland	MyHome.ie Scraper
🇩🇰 Denmark	Boliga Scraper

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Put this Actor on an Apify Schedule for a fresh WG-Gesucht listings feed every morning, straight to the Apify API, a webhook, Google Sheets, S3 or your warehouse. Chain searches across cities and categories to build a nationwide German rental dataset. Connect it to Make, n8n or Zapier for automated rental-monitoring pipelines.

⭐ Support & feedback

Found a bug or need an extra field? Open an issue on the Issues tab — response is usually fast. If this Actor saves you time, a ★★★★★ review on the Store page genuinely helps and is hugely appreciated. 🙏

⚖️ Legal

This Actor extracts only publicly available data and is intended for legitimate research, analytics and market-monitoring use. You are responsible for complying with WG-Gesucht's terms of service, the GDPR and any applicable local laws — including how you use any personal data in the listings.

---

This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by WG-Gesucht; WG-Gesucht and all other trademarks mentioned here are the property of their respective owners.

How much Wg data can you extract in one run?

A single run returned 342 rows in 138 seconds on the example input. That example is deliberately narrow; the result limit and the input list are both yours to widen. That is roughly 148 rows a minute.

There is no hard ceiling built into this Actor. What bounds a run is the result limit you set, the breadth of the input you give it, and how much Wg itself publishes. Because billing is per result, a wider run costs proportionally more and a narrow one costs almost nothing — so it is worth starting small and scaling once the output looks right.

Wg scraping — frequently asked questions

Do I need a Wg API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Wg data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Wg scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the rows you care about really do change that fast.

How many rows can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

Is scraping Wg legal?

This Actor collects only information that Wg publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Wg blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

📝 Changelog

2026-11-01

• Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
• README refreshed: 1 link to retired Actors removed; independence disclaimer added; documented 3 additional input fields.

2026-10-15

• Fixed: runs were finishing with no listings because WG-Gesucht redesigned its listing cards (the title, price, size, dates and poster moved); the parser reads the new cards and keeps the old layout as a fallback.
• Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
• A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
• A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
• Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
• Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
• The default used when the field is left out for maxResults is now 2,973 (was 200).

2026-09-23

• Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
• Output verified on a live run: 19 columns returned, 96.7% of cells populated.
• Run reliability reviewed: 100.0% of public runs succeeded in the last 30 days.
• Input schema, output schema and pricing configuration reviewed.

2026-09-01

• Fleet-wide health check. Verified against this Actor's real run history: 30-day success rate, output row counts, per-field fill rates, and peak memory against the configured memory limit.
• Reviewed for the failure patterns that have cost this fleet runs — unguarded proxy setup, retry loops that can outlast the run's own time budget, and full-page HTML parsing that can exhaust a small container.
• No change to input, output fields or scraping logic.

2026-08-11

• Maintenance release: refreshed the build and dependencies.
• Re-verified live execution, non-empty structured output and dataset field/type integrity.
• Reviewed reliability (retries, pagination) and output quality as part of a full-fleet QA pass.

2026-08-01

• Completed the August 2026 full health check: verified empty/programmatic default, Console UI default, and two source-informed alternative inputs on Apify.
• Confirmed successful live execution, non-empty structured output, dataset-field/type integrity, and logical sample quality within the 5-minute quality window.
• Declared 19 dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder.
• Declared 19 nullable dataset fields from typed live cloud samples so the output contract is no longer an empty placeholder or brittle to sparse modes.

2026-07-06

• ✨ README overhaul: shields badge row, green highlight callout, collapsible full field reference, extra ready-to-run example scenarios, cross-country real-estate suite links and clearer quick-start.

2026-07-01

• Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
• Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
• Added ready-to-run example tasks that cover common real-world use cases.

2026-06-15

• Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.

2026-06-07

• Docs: added coverage for using this as a WG-Gesucht API alternative, exporting WG-Gesucht data to CSV/JSON, and scraping WG-Gesucht without login.

License

Apache-2.0

---

*Maintained: last verified 2026-11-01 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).