# Local.ch $1💰 Listings | URLs | Reviews Scraper (`abotapi/local-ch-scraper`) Actor

From $1/1K. Pull structured company data from local.ch, including name, address, GPS, phone, email, website, hours, ratings, social links, photos, and categories. Search by category and location or use URLs. Supports Deutsch, English, Français, and Italiano.

- **URL**: https://apify.com/abotapi/local-ch-scraper.md
- **Developed by:** [Abot API](https://apify.com/abotapi) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 8 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## local.ch Scraper

Pull structured company data from **local.ch**, the Swiss directory: name, full street address, GPS coordinates, phone, email, website, opening hours, ratings, social media URLs, photos, and category tags. Two ways to start: search by category and location (city, postal code, canton, or all of Switzerland), or paste local.ch URLs (search or company profiles). Works in Deutsch, English, Français, and Italiano.

### Why this scraper

- **Two start modes plus a review-only switch**: search by category + location, or paste local.ch URLs. Turn on `reviewOnly` to emit review-comment rows instead of listings.
- **Four languages**: pages and category slugs auto-resolve in DE/EN/FR/IT, so `coiffeur` works in French and `friseur` works in German.
- **Five location types**: city slug (`zurich`), 4-digit postal code (`8001`), 2-letter canton (`zh`, `ge`, `vd`), `switzerland`, or all of Switzerland.
- **30+ fields per company**, including phone, mobile, email, website, all social media URLs (Facebook, Instagram, LinkedIn, X, TikTok, Pinterest, YouTube, XING), GPS lat/lng, opening hours per weekday, attribute tags (delivery, takeaway, parking, ...), and full photo galleries.
- **Detail enrichment by default** (toggle via `fetchDetails`): SERP cards alone only carry name + city + postal + category, so the actor visits every profile to pull the rich payload.
- **Optional review comments in listing rows**: turn on `includeReviews` to embed up to 10 review comments per search or URL mode listing.
- **Polymorphic `contactsRaw[]` passthrough**: the full contact polymorphism (MobileContact, LandlineContact, EmailContact, SocialMediaContact, ...) is preserved alongside the flat fields, so future-added contact types still land in the dataset.
- **Tiny footprint**: 256 MB peak memory, runs on the Apify free tier.

### Data you get

> Sample shape, values are illustrative placeholders, not from a live company.

| Field | Example |
| --- | --- |
| `id` | `aaaaaaaaaaaaaaaaaaaaaa` |
| `name` | `Sample Café Zürich` |
| `subtitle` | `Sample Café GmbH` |
| `language` | `de` |
| `isPremium` | `true` |
| `mainCategory` | `Café` |
| `mainCategorySlug` | `cafe` |
| `categories` | `["Café", "Tea room", "Catering"]` |
| `categorySlugs` | `["cafe", "tea-room", "catering"]` |
| `street` | `Sample Street 1` |
| `zipCode` | `8001` |
| `city` | `Zürich` |
| `canton` | `ZH` |
| `country` | `CH` |
| `address` | `Sample Street 1, 8001 Zürich` |
| `latitude` | `47.0000` |
| `longitude` | `8.0000` |
| `phone` | `+41440000000` |
| `mobile` | `+41760000000` |
| `email` | `info@example.com` |
| `website` | `https://example.com/` |
| `whatsapp` | `+41760000000` |
| `facebook` | `https://www.facebook.com/example` |
| `instagram` | `https://www.instagram.com/example` |
| `linkedin` | `https://www.linkedin.com/company/example` |
| `rating` | `4.5` |
| `ratingCount` | `120` |
| `reviewCount` | `60` |
| `reviewsFetched` | `3` |
| `reviews` | `[{ "text": "Great service...", "author": "Reviewer", "date": "2026-01-01" }]` |
| `reviewText` | `Great service and friendly staff. (review mode only)` |
| `openingHours` | `Mon: 09:00-18:00; Tue: 09:00-18:00; Wed: closed; ...` (always lists all 7 days) |
| `openingHoursStructured` | `[{ day: "MONDAY", status: "open", byArrangement: false, intervals: [{ type: "OPEN", start: "09:00", end: "18:00" }] }, ...]` (all 7 days; `status` ∈ `open`/`closed`/`by_arrangement`) |
| `openingHoursByArrangement` | `false` (listing-level flag — `true` when any day is "by arrangement" / *nach Vereinbarung*) |
| `description` | `Sample description paragraph appears here when fetchDetails=true.` |
| `attributes` | `["Takeaway", "Delivery", "Vegetarian options"]` |
| `breadcrumb` | `["Home", "Food", "Café"]` |
| `logoUrl` | `https://images.services.local.ch/.../logo.jpg` |
| `imageUrls` | `["https://images.services.local.ch/.../photo-1.jpg", "..."]` |
| `contactsRaw` | full polymorphic contacts array (see Output example) |
| `attributeGroupsRaw` | full upstream attributeGroups array |
| `detailUrl` | `https://www.local.ch/de/d/zurich/8001/cafe/sample-cafe-zurich-aaaaaaaaaaaaaaaaaaaaaa` |
| `searchQuery` | `cafe` |
| `searchWhere` | `zurich` |

### How to use

**Search by category in one city**

```json
{
  "mode": "search",
  "category": "restaurant",
  "where": "zurich",
  "language": "de",
  "maxPages": 5,
  "fetchDetails": true
}
```

**Multi-category sweep across a canton**

```json
{
  "mode": "search",
  "queries": ["restaurant", "hotel", "café"],
  "where": "zh",
  "language": "de",
  "maxListings": 200
}
```

**Search by 4-digit postal code, English UI**

```json
{
  "mode": "search",
  "category": "tea-room",
  "where": "8001",
  "language": "en",
  "maxPages": 3
}
```

**Paste local.ch URLs (search + profile mixed)**

```json
{
  "mode": "url",
  "urls": [
    "https://www.local.ch/de/s/restaurant/zurich",
    "https://www.local.ch/fr/s/restaurant/geneve",
    "https://www.local.ch/en/d/zurich/8001/tea-room/sample-name-aaaaaaaaaaaaaaaaaaaaaa"
  ],
  "maxPages": 3,
  "fetchDetails": true
}
```

**Listing records with review comments embedded**

```json
{
  "mode": "url",
  "urls": [
    "https://www.local.ch/en/d/zurich/8001/tea-room/bonne-maman-boutique-cafe-nVESaL0TOav64BpX8B1Ncg"
  ],
  "includeReviews": true,
  "maxReviewsPerListing": 10
}
```

**Review comments only from pasted profile URLs**

```json
{
  "mode": "url",
  "reviewOnly": true,
  "urls": [
    "https://www.local.ch/en/d/zurich/8001/tea-room/bonne-maman-boutique-cafe-nVESaL0TOav64BpX8B1Ncg"
  ],
  "maxListings": 10
}
```

**Review comments discovered from a category search**

```json
{
  "mode": "search",
  "reviewOnly": true,
  "category": "restaurant",
  "where": "zurich",
  "maxListings": 10
}
```

**Lead-gen filter: only premium-listed companies with both phone and email**

```json
{
  "mode": "search",
  "category": "garage",
  "where": "switzerland",
  "language": "de",
  "premiumOnly": true,
  "withPhone": true,
  "withEmail": true,
  "maxListings": 500
}
```

### Input parameters

| Parameter | Type | Default | Description |
| --- | --- | --- | --- |
| `mode` | string | `search` | `search` (build from category + location) or `url` (use the `urls` list). |
| `reviewOnly` | boolean | `false` | Global output switch. When `true`, emit one row per review comment instead of listing rows. |
| `category` | string | `restaurant` | Single category slug or label. Used in search mode when `queries` is empty. |
| `queries` | array<string> | `[]` | Multiple categories to walk in search mode. Overrides `category`. |
| `where` | string | `zurich` | Location: city slug, 4-digit postal code, 2-letter canton, `switzerland`, or empty. |
| `language` | enum | `de` | `de`, `en`, `fr`, or `it`. Affects URL slugs and content language. |
| `urls` | array<string> | `[]` | local.ch URLs (search or profile pages). Used in URL mode. With `reviewOnly=true`, profile URLs scrape reviews directly and search URLs discover profiles, then scrape reviews. |
| `maxPages` | integer | none (unlimited) | Optional bound on result pages walked per category/URL (20 results each). Leave empty to walk every page. |
| `maxListings` | integer | `20` | Total cap (0 = unlimited). Multi-query inputs split the cap evenly. |
| `fetchDetails` | boolean | `true` | Visit each profile page for phone, email, GPS, hours, social, attributes. |
| `includeReviews` | boolean | `false` | Include review comments inside each search or URL mode listing record. |
| `maxReviewsPerListing` | integer | `10` | Maximum embedded review comments per listing. Capped at 10. |
| `maxReviewRows` | integer | `10` | Default review-row cap when `reviewOnly=true` and `maxListings` is explicitly set to 0. |
| `maxConcurrency` | integer | `6` | No longer user-configurable. Detail-fetch concurrency is fixed internally at the reliable default (kept in the schema only so saved task inputs keep validating). |
| `resumeFromRunId` | string | none | Paste a previous run/dataset ID to skip rows it already collected and return only new ones. Continues ONE specific interrupted run — for recurring monitoring of the same search, use `incrementalMode` instead. |
| `incrementalMode` | boolean | `false` | Turn on for daily/recurring monitoring of the same search/URL/review scope. First run returns everything as `NEW`; later runs return only `NEW`/`UPDATED`/`REAPPEARED` rows (each carrying `changeType`, `changedFields`, `firstSeenAt`, `lastSeenAt`). State is kept per search/filter/review setup automatically, or under `stateKey` if set. |
| `stateKey` | string | none | Incremental mode only. Name a monitoring campaign to keep its state stable or deliberately share it across runs. Leave empty to derive a key automatically from the search/filter/review setup. |
| `emitUnchanged` | boolean | `false` | Incremental mode only. Also return (and bill) rows unchanged since the last run, marked `UNCHANGED`. |
| `emitExpired` | boolean | `false` | Incremental mode only. Also return (and bill) rows tracked previously but no longer found, marked `EXPIRED`. Only produced after a run proves a complete scan (no cap hit, no resume). |
| `ratedOnly` | boolean | `false` | Drop entries without an average rating. |
| `minRating` | number | (none) | Drop entries below this rating. |
| `withPhone` | boolean | `false` | Drop entries without a phone number. Search-result cards never carry a phone number, so turning this on forces `fetchDetails` on too, regardless of what it was set to. |
| `withEmail` | boolean | `false` | Drop entries without an email. Forces `fetchDetails` on for the same reason as `withPhone`. |
| `withWebsite` | boolean | `false` | Drop entries without a website. Forces `fetchDetails` on for the same reason as `withPhone`. |
| `premiumOnly` | boolean | `false` | Keep only premium-listed companies. Forces `fetchDetails` on for the same reason as `withPhone`. |
| `matchQueryPostalCode` | boolean | `false` | Search mode only. When the location is a postal code, keep only results whose postal code exactly matches the queried one and drop the rest before any detail fetch. local.ch's search isn't strictly postal-code-bound — when few exact matches exist it pads the page with other regions; this removes them. |
| `skipRegionalFallback` | boolean | `false` | Search mode only. When a query has zero exact matches, local.ch silently falls back to a region-wide search and returns unrelated results. When enabled, the actor detects this fallback and emits no output for that query (no detail fetch, no rows). |
| `proxy` | object | `{ useApifyProxy: true }` | Defaults to Apify's standard connection settings. For large runs, country=CH is recommended. |

### Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step **after** the scrape — the Apify dataset is never changed.

**What gets written to the connector:** a condensed, human-readable **summary** of each record — not the full JSON. Each item becomes one entry with a **title** and its key fields flattened to plain text. The **complete record always stays in the Apify dataset**.

1. Authorize a connector once under **Apify → Settings → Integrations** (Notion, Linear, Airtable, or Apify).
2. Select it in the **"Pipe results into your apps"** input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For **Notion**, also set `notionParentPageUrl` to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

### Output example

> Sample record, values are illustrative placeholders, not from a live company.

```json
{
  "id": "aaaaaaaaaaaaaaaaaaaaaa",
  "name": "Sample Café Zürich",
  "subtitle": "Sample Café GmbH",
  "language": "de",
  "isPremium": true,
  "favorited": false,
  "professionalTitle": null,
  "address": "Sample Street 1, 8001 Zürich",
  "street": "Sample Street 1",
  "zipCode": "8001",
  "city": "Zürich",
  "canton": "ZH",
  "country": "CH",
  "latitude": 47.0000,
  "longitude": 8.0000,
  "phone": "+41440000000",
  "phoneAlt": null,
  "mobile": "+41760000000",
  "fax": null,
  "email": "info@example.com",
  "emailAlt": null,
  "website": "https://example.com/",
  "whatsapp": "+41760000000",
  "facebook": "https://www.facebook.com/example",
  "instagram": "https://www.instagram.com/example",
  "linkedin": "https://www.linkedin.com/company/example",
  "twitter": null,
  "tiktok": null,
  "pinterest": null,
  "youtube": null,
  "xing": null,
  "foursquare": null,
  "mainCategory": "Café",
  "mainCategorySlug": "cafe",
  "categories": ["Café", "Tea room", "Catering"],
  "categorySlugs": ["cafe", "tea-room", "catering"],
  "rating": 4.5,
  "ratingCount": 120,
  "reviewCount": 60,
  "reviewsFetched": 2,
  "reviews": [
    {
      "reviewId": "aaaaaaaaaaaaaaaa",
      "title": "Great service",
      "text": "Sample review comment appears here.",
      "date": "2026-01-01T10:00:00Z",
      "author": "Reviewer Name",
      "reply": null
    }
  ],
  "openingHours": "Mon: 09:00-18:00; Tue: 09:00-18:00; Wed: closed; Thu: 09:00-18:00; Fri: 09:00-18:00; Sat: 10:00-17:00; Sun: closed",
  "openingHoursStructured": [
    { "day": "MONDAY", "status": "open", "byArrangement": false, "intervals": [{ "type": "OPEN", "start": "09:00", "end": "18:00" }] },
    { "day": "WEDNESDAY", "status": "closed", "byArrangement": false, "intervals": [] }
  ],
  "openingHoursByArrangement": false,
  "description": "Sample description paragraph appears here when fetchDetails=true.",
  "descriptionHtml": "<p>Sample description paragraph appears here when fetchDetails=true.</p>",
  "attributes": ["Takeaway", "Delivery", "Vegetarian options"],
  "breadcrumb": ["Home", "Food", "Café"],
  "logoUrl": "https://images.services.local.ch/aaaa/logo.jpg",
  "imageUrls": [
    "https://images.services.local.ch/aaaa/photo-1.jpg",
    "https://images.services.local.ch/aaaa/photo-2.jpg"
  ],
  "contactsRaw": [
    { "__typename": "MobileContact", "value": "+41760000000", "displayValue": "076 000 00 00", "whatsapp": true },
    { "__typename": "EmailContact",  "value": "info@example.com", "displayValue": "info@example.com" },
    { "__typename": "CustomerProvidedURLContact", "value": "https://example.com/", "displayValue": "example.com" },
    { "__typename": "SocialMediaContact", "value": "https://www.facebook.com/example", "socialMediaProvider": "FACEBOOK" }
  ],
  "additionalContactsRaw": null,
  "attributeGroupsRaw": [
    { "groupName": "Services", "attributes": [{ "id": "takeaway", "name": "Takeaway" }] }
  ],
  "detailUrl": "https://www.local.ch/de/d/zurich/8001/cafe/sample-cafe-zurich-aaaaaaaaaaaaaaaaaaaaaa",
  "searchQuery": "cafe",
  "searchWhere": "zurich"
}
```

### Plan requirement

The actor works on every Apify plan including **Free**. For larger runs (thousands of records), the **Apify Starter plan or above** is recommended for the most consistent throughput.

# Actor input Schema

## `mode` (type: `string`):

Choose where the actor should start. Search mode builds searches from category and location. URL mode uses pasted local.ch URLs.

## `reviewOnly` (type: `boolean`):

When ON, output one row per review comment instead of profile listing rows. Works in both search and URL modes.

## `category` (type: `string`):

Used in search mode. Examples: `restaurant`, `coiffeur`, `hairdresser`, `dentist`, `garage`, `hotel`.

## `queries` (type: `array`):

Used in search mode. Optional list of categories to search. When set, this overrides the single `category` field.

## `where` (type: `string`):

Used in search mode. Examples: city slug (`zurich`), postal code (`8001`), canton code (`zh`), or `switzerland`.

## `language` (type: `string`):

Used for URLs and page content. local.ch supports German, English, French, and Italian.

## `urls` (type: `array`):

Used in URL mode. Paste one or more local.ch URLs.
• Search URL: walks result pages
• Profile URL: scrapes one profile page

With `reviewOnly=true`, the actor outputs review comments instead of listing rows.

## `maxPages` (type: `integer`):

Optional bound on result pages walked per category/keyword/URL. Leave empty to walk every result page.

## `maxListings` (type: `integer`):

Maximum dataset rows to output. Listing rows when `reviewOnly=false`, review rows when `reviewOnly=true`.

## `fetchDetails` (type: `boolean`):

When ON, enrich listing rows with profile-page fields like phone, email, full address, coordinates, opening hours, social links, and attributes.

## `includeReviews` (type: `boolean`):

Listing output only. Embed review comments inside each listing row. Ignored when `reviewOnly=true`.

## `maxReviewsPerListing` (type: `integer`):

Listing output only. Maximum review comments to embed in each listing row. Values above 10 are capped to 10.

## `maxReviewRows` (type: `integer`):

Review-only output only. Default review-row cap when `reviewOnly=true` and `maxListings=0`.

## `maxConcurrency` (type: `integer`):

Deprecated and ignored. Detail-fetch concurrency is fixed internally at the reliable default; the input is kept only so saved task inputs keep validating.

## `resumeFromRunId` (type: `string`):

Optional: paste a previous run ID (or dataset ID) from this actor. Rows already collected there are skipped, so this run only returns new ones. Use this after an interrupted run, or to continue a large pull in another run. For recurring monitoring of the same search, use Incremental mode below instead.

## `incrementalMode` (type: `boolean`):

Turn this on for daily or recurring monitoring of the same search/URL/review scope. The first run returns all matching rows as NEW. Later runs normally return only NEW, UPDATED, and REAPPEARED rows. Turn on "Emit unchanged" or "Emit expired" only when you also want those rows returned (and billed). State is kept separately per search/URL/filter/review setup; use State key when you want to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from run ID above.

## `stateKey` (type: `string`):

Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently-configured runs. Leave empty to let the actor derive a key automatically from the search/URL/filter/review setup — different setups then never mix state with each other.

## `emitUnchanged` (type: `boolean`):

Off by default. Turn on to also return rows that have not changed since the last run, marked UNCHANGED. This returns — and bills — extra rows you already have, so leave it off unless you specifically want the full snapshot every run.

## `emitExpired` (type: `boolean`):

Off by default. Turn on to also return rows that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked search — not when Max pages/rows capped it or when Resume was used. This returns — and bills — extra synthetic rows, so leave it off unless you need expiry tracking.

## `ratedOnly` (type: `boolean`):

Listing output only. Keep only listing rows that have an average rating.

## `minRating` (type: `integer`):

Listing output only. Keep only listing rows at or above this rating.

## `withPhone` (type: `boolean`):

Listing output only. Keep only listing rows with a phone number. This data only exists on the profile page, so turning this on also enables Fetch detail pages, regardless of that toggle.

## `withEmail` (type: `boolean`):

Listing output only. Keep only listing rows with an email address. This data only exists on the profile page, so turning this on also enables Fetch detail pages, regardless of that toggle.

## `withWebsite` (type: `boolean`):

Listing output only. Keep only listing rows with a website. This data only exists on the profile page, so turning this on also enables Fetch detail pages, regardless of that toggle.

## `premiumOnly` (type: `boolean`):

Listing output only. Keep only premium-listed profiles. This data only exists on the profile page, so turning this on also enables Fetch detail pages, regardless of that toggle.

## `matchQueryPostalCode` (type: `boolean`):

Search mode only. When ON and the location is a postal code (e.g. `8001`), keep only results whose postal code exactly matches the queried one, and skip the rest before any detail-page fetch (saves proxy GB). local.ch's search is not strictly postal-code-bound — when few exact matches exist it pads the page with other regions — so this removes those off-target hits. Default OFF preserves current behaviour.

## `skipRegionalFallback` (type: `boolean`):

Search mode only. When a query has zero exact matches, local.ch silently falls back to a region-wide search and shows unrelated results (e.g. `psychologie` in `1346`). When ON, the actor detects this fallback and emits no output for that query — no detail-page fetch, no rows. Default OFF preserves current behaviour.

## `proxy` (type: `object`):

Proxy settings. Swiss residential is recommended — local.ch serves large pages and the shared datacenter pool can stall on them. If residential isn't on your plan, the actor automatically falls back to a datacenter and then a backup pool.

## `mcpConnectors` (type: `array`):

Optionally send the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize a connector once under Apify → Settings → Integrations, then select it here. The connector receives a condensed, human-readable summary per item (title + key fields), not the full JSON — the complete record stays in the dataset. Leave empty to skip. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com).

## `notionParentPageUrl` (type: `string`):

URL (or id) of the Notion page under which item pages are created. Required to enable the Notion export; ignored by other connectors.

## `maxNotifyListings` (type: `integer`):

Cap on items written to each connector per run. Does not affect the dataset.

## Actor input object example

```json
{
  "mode": "search",
  "reviewOnly": false,
  "category": "restaurant",
  "queries": [],
  "where": "zurich",
  "language": "de",
  "urls": [
    "https://www.local.ch/de/s/restaurant/zurich"
  ],
  "maxListings": 20,
  "fetchDetails": true,
  "includeReviews": false,
  "maxReviewsPerListing": 10,
  "maxReviewRows": 10,
  "maxConcurrency": 6,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "ratedOnly": false,
  "withPhone": false,
  "withEmail": false,
  "withWebsite": false,
  "premiumOnly": false,
  "matchQueryPostalCode": false,
  "skipRegionalFallback": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CH"
  },
  "maxNotifyListings": 50
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "mode": "search",
    "urls": [
        "https://www.local.ch/de/s/restaurant/zurich"
    ],
    "maxPages": 0,
    "maxListings": 20,
    "incrementalMode": false,
    "emitUnchanged": false,
    "emitExpired": false,
    "proxy": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "CH"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("abotapi/local-ch-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "mode": "search",
    "urls": ["https://www.local.ch/de/s/restaurant/zurich"],
    "maxPages": 0,
    "maxListings": 20,
    "incrementalMode": False,
    "emitUnchanged": False,
    "emitExpired": False,
    "proxy": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "CH",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("abotapi/local-ch-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "mode": "search",
  "urls": [
    "https://www.local.ch/de/s/restaurant/zurich"
  ],
  "maxPages": 0,
  "maxListings": 20,
  "incrementalMode": false,
  "emitUnchanged": false,
  "emitExpired": false,
  "proxy": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "CH"
  }
}' |
apify call abotapi/local-ch-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abotapi/local-ch-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/gNFS0YaXb7eRJ2TgA/builds/W73d88ZV2C1BkGGjk/openapi.json