Comparis.ch Listings Scraper with Public Emails

Search public Comparis.ch car or real-estate results and return structured listing records. The actor is designed for Swiss automotive dealers, property researchers, aggregators, and AI agents that need a bounded search-to-JSON workflow.

What it extracts

Each dataset item contains the listing URL and ID, title, price/currency, location, seller name and phone when visible, image URL, description, category, and an emails array. Email extraction is limited to addresses publicly displayed in the listing page or public mailto: links; the actor does not log in, guess addresses, or access private contact details.

Input

Use category: "cars" for the car finder, category: "real_estate" for the property market, or category: "custom" with a public Comparis search URL. maxResults defaults to 25 and is capped at 200. maxPages defaults to 5. Detail pages and public email extraction are enabled by default.

{
  "category": "cars",
  "searchUrl": "https://www.comparis.ch/carfinder/default",
  "maxResults": 25,
  "maxPages": 5,
  "scrapeDetails": true,
  "extractEmails": true,
  "proxyCountry": "CH"
}

Output and reliability

The dataset contains one normalized item per unique listing URL. The OUTPUT and SUMMARY key-value records include the count and warnings. Empty searches are successful. If Comparis returns an anti-bot challenge, rate-limit response, or a changed page structure, the actor returns a diagnostic warning instead of silently returning misleading data.

Pricing and limits

The intended Store billing model is one start event plus one primary event per listing. Keep result caps low while testing, then increase them for production. Residential proxy usage and listing detail navigation can materially increase runtime and cost.

Legal and responsible use

Use only public data and comply with Comparis.ch terms, applicable Swiss data-protection law, and any source marketplace restrictions. Do not use extracted contact details for unlawful spam or sensitive profiling.

Use cases

• Build public prospect lists and qualify organizations or professionals before responsible outreach.
• Compare listings, locations, availability, and market signals for property research.
• Run a one-off research job and export the structured result as JSON, CSV, Excel, XML, or RSS from Apify.
• Schedule the same input to monitor changes over time and send completed datasets to a webhook or integration.
• Feed schema-shaped records into a database, spreadsheet, BI tool, or AI workflow with the source URL retained for verification.

Run Comparis.ch Listings Scraper with Public Emails with the Apify API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/comparis-ch-scraper').call({
  "category": "cars",
  "searchUrl": "",
  "maxResults": 3,
  "maxPages": 1,
  "scrapeDetails": true,
  "extractEmails": true,
  "proxyCountry": "CH"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

You can also run the Actor from Apify Console, schedules, webhooks, the REST API, Make, Zapier, n8n, or the hosted Apify MCP server.

Support

When reporting a problem, include the Actor run ID, a redacted input, the expected result, and a small public example URL when applicable. Do not post API tokens, cookies, credentials, or personal data in an issue.

Frequently asked questions

Can I schedule Comparis.ch Listings Scraper with Public Emails?

Yes. Use an Apify schedule to run the same saved input at a chosen interval, then connect a webhook or integration to process the dataset when the run finishes.

How should I test a new input?

Begin with the prefilled example or a small limit. Confirm that the output fields, source coverage, runtime, and live charges match your workflow before increasing the scope.

How do I export the results?

Open the run's default dataset in Apify Console and export JSON, CSV, Excel, XML, or RSS. Applications can retrieve the same records through the Apify API client or REST dataset endpoint.

Can an AI agent call this Actor?

Yes. Add muhammadafzal/comparis-ch-scraper through the hosted Apify MCP server or call it through the API. The Actor's input and dataset schemas help agents construct valid requests and interpret returned records.

Recommended workflow

1. Define the smallest useful scope. Choose a representative public URL, query, identifier, or filter and keep the first result limit low.
2. Run and inspect. Check the run log, dataset item count, field coverage, source URLs, and live event or usage charges.
3. Validate downstream assumptions. Confirm nullable fields, deduplication keys, timestamps, and any locale-specific formats before importing records into another system.
4. Scale gradually. Increase limits or scheduling frequency only after the small run behaves as expected. Use Apify's maximum-cost and timeout controls to bound large jobs.
5. Monitor changes. Keep a small known-good input as a canary. If the source layout or API changes, compare the new dataset with a previously validated run and report the run ID when requesting support.

For recurring workflows, store the exact Actor input with your pipeline configuration. This makes runs reproducible and helps distinguish a source-data change from an input change.