Switzerland Government Data Search

Search Switzerland-focused public data across business, construction, health, legal, and procurement products in one run.

• ✅ Search 25 Switzerland-focused SIP data products with one keyword list
• ✅ Cover cantonal company data, LEI entities, SNB rates, building and planning data, clinical and legal sources, and procurement datasets
• ✅ Use it without coding, or connect it to ChatGPT, Claude, MCP, Make, Zapier, or n8n
• ✅ Turn categories on only when you need them
• ✅ Free $5 Apify credit is enough to test real searches before you pay anything

Swiss public data is distributed across cantonal, federal, international, and catalog-based systems. Company data is not centralized into one single national commercial register. Building and planning data is also split across cantonal and federal sources. This Actor gives you one search layer across Switzerland-focused SIP products, then returns structured results in a single dataset you can review, export, or feed into downstream workflows.

This Actor is best for discovery, topic scanning, monitoring, and early-stage research. It is not a substitute for deep canton-by-canton analysis, and it does not turn all Swiss public data into one perfectly standardized national master database.

---

What you can do with it

1. Search Swiss company and entity signals across cantons

If you are doing Swiss entity research, start with the business category.

What you enter

• Search terms like Nestlé, Basel, insurance, holding, pharma
• Keep business & company data enabled

What you get back

• Basel-Stadt commercial register matches
• Basel-Landschaft commercial register matches
• Thurgau commercial register matches
• GLEIF LEI entity matches
• opendata.swiss business catalog entries
• SNB exchange-rate records
• Business aggregate results

This is useful when you want a fast answer to questions like:

• Does this entity appear in cantonal public company data?
• Is there a matching LEI record?
• Which Swiss public-data products should I inspect more deeply next?

2. Search Swiss building, permit, and construction context

If your topic is development, property, building stock, or construction, the construction category gives you a broader entry point than any single canton alone.

What you enter

• Search terms like Basel, building permit, construction, residential, industrial
• Keep construction & building data enabled

What you get back

• Basel-Stadt building permit matches
• Basel-Stadt and Basel-Landschaft building records
• geo.admin.ch federal building register matches
• opendata.swiss construction catalog entries
• Construction aggregate results

This works well when you want a first-pass view of building and construction context without manually checking multiple portals.

3. Search Swiss health and clinical datasets

The health category is useful when you want Switzerland-related public-health or clinical signals from multiple products at once.

What you enter

• Search terms like oncology, hospital, trial, mortality, health expenditure
• Keep health & clinical data enabled

What you get back

• Swiss clinical trial records
• WHO health indicator matches for Switzerland
• opendata.swiss health catalog entries
• Health aggregate results

This is useful for healthcare discovery, public-health scanning, and clinical-data sourcing.

4. Search Swiss legal, legislative, and procurement sources

Legal and procurement are off by default, but they can be enabled when you want a broader public-sector scan.

What you enter

• Search terms like federal law, agreement, public tender, transport, energy
• Enable legal & legislative data and/or public procurement

What you get back

• Fedlex legislation matches
• Swiss Parliament affairs matches
• EUR-Lex Swiss bilateral agreement matches
• opendata.swiss legal or procurement catalog entries
• TED procurement results for Switzerland
• Aggregate legal or procurement results

This is useful when you want to connect legislation, parliamentary affairs, and procurement discovery in one search pass.

5. Connect Swiss public-data discovery to AI or automation

This Actor works for manual use, but it is also designed to plug into broader workflows.

What you enter

• Search terms and category toggles in Apify
• Or the same parameters through API, MCP, or automation tools

What you get back

• Structured records in the dataset
• Stable SIP metadata fields such as _product_id, _source, _search_term, and _collected_at
• Output that is easy to export, summarize, monitor, or pass into spreadsheets and AI agents

This is the right pattern when you want search once, reuse everywhere.

---

How to use

You do not need to write code to use this Actor.

1. Open the Actor and click Try for free
2. Enter one or more search terms such as Nestlé, Basel, trial, or Fedlex
3. Choose which categories to include:
   • business & company data
   • construction & building data
   • health & clinical data
   • legal & legislative data
   • public procurement
4. Set max results per source
5. Run the Actor
6. Review the results in Apify or export them as JSON, CSV, Excel, XML, or RSS

By default, business, construction, and health are enabled. Legal and procurement are available when you want a broader scan.

---

What you get back

The Actor returns structured records from the selected Switzerland-focused products. Exact fields vary by source, because a cantonal company record, an SNB exchange-rate row, a building permit, a clinical trial, and a Fedlex legal record are not the same kind of object.

Common SIP metadata fields include:

Field	What it means
_product_id	The SIP product that returned the record
_source	Human-readable source label
_search_term	The keyword that produced the record
_collected_at	UTC collection timestamp

In the Output tab, the default overview highlights fields such as:

• name
• type
• canton
• status
• _source
• _search_term
• _collected_at

Depending on the enabled category, you may also see fields like:

• company_name
• uid
• lei
• exchange_rate
• canton
• building_id
• trial_id
• indicator
• short_title
• buyer
• source_url

Here is a simplified example:

[
  {
    "company_name": "Nestle SA",
    "uid": "CHE-102.919.882",
    "status": "active",
    "canton": "VD",
    "_product_id": "ch_gleif_lei",
    "_source": "gleif_lei",
    "_search_term": "Nestlé"
  },
  {
    "building_id": "BS-12345",
    "canton": "BS",
    "status": "published",
    "_product_id": "ch_bs_building_permits",
    "_source": "bs_building_permits",
    "_search_term": "Basel"
  }
]

The goal is not to force every Swiss source into identical semantics. The goal is to make cross-source discovery fast enough to act on.

---

Coverage

This Actor currently searches 25 Switzerland-focused SIP data products across 5 categories:

Category	What is included	Count
Business	Cantonal company products, GLEIF, SNB, business catalog, business aggregate	7
Construction	Building permits, building registers, geo.admin.ch, construction catalog, construction aggregate	6
Health	Swiss clinical trials, WHO indicators, health catalog, health aggregate	4
Legal	Fedlex, Parliament affairs, EUR-Lex bilateral, legal catalog, legal aggregate	5
Procurement	TED procurement, procurement catalog, procurement aggregate	3

There are two important boundaries to state clearly.

First:

• These are 25 SIP data products, not 25 completely separate Swiss institutions
• Some products are direct record-style sources
• Some are aggregate or catalog products layered on top of narrower source products

Second:

• Some products return entity or record-style data like cantonal company records, building entries, or trial records
• Some return catalog-style metadata from opendata.swiss
• Some return cross-border or international context such as GLEIF, WHO, EUR-Lex, or TED scoped to Switzerland-relevant data

So the right mental model is: this Actor is a Switzerland public-data discovery layer across multiple source types, not a single fully standardized Swiss national master database.

---

Pricing

This Actor is currently listed on Apify with pay per usage pricing.

That means your cost depends on:

• your Apify plan
• how often you run the Actor
• how many results you return
• how many categories and sources you enable

For the current pricing page, see:

• https://apify.com/lentic_clockss/switzerland-data-search/pricing

In practice, the free Apify credit is enough to test real searches, inspect the output shape, and decide whether this workflow fits your research or automation use case before you pay anything.

---

Connect to your tools

You can use this Actor manually or connect it to your stack.

Tool	How to use it
Apify Console	Run it directly with a form input
Make.com	Use the Actor via Apify integration
Zapier / n8n	Trigger runs and send results into downstream workflows
ChatGPT / Claude	Connect through Apify MCP
Scripts / apps	Call it through the Apify API

If you want to use it with AI workflows, Apify MCP is usually the cleanest path.

---

When to use something else

This Actor is a strong fit when you want a broad Switzerland public-data entry point across companies, buildings, health, law, and procurement topics.

Choose something else if you already know you need a narrower or deeper workflow:

• Use a company-registry-specific workflow if you need deep canton-by-canton entity research
• Use a building or planning-specific workflow if you need permit-level or parcel-level operational work
• Use a legal-specific workflow if you need full legislative analysis rather than mixed-source discovery
• Use a procurement-specific workflow if you need dedicated tender operations rather than broad public-data lookup

In short, this Actor is best for finding relevant Switzerland public data quickly, not for replacing every source-specific operational workflow.

---

FAQ

Q: Does this search all Swiss government data?
A: No. It searches 25 Switzerland-focused SIP data products across 5 categories. That is broad coverage, but not the whole Swiss public-data universe.

Q: Are all 25 sources fully independent Swiss institutions?
A: No. The 25 count includes aggregate and catalog products as well as narrower record-style products.

Q: Does it include only Swiss-native sources?
A: No. It also includes Switzerland-relevant products from GLEIF, WHO, EUR-Lex, and TED where those sources materially support Swiss workflows.

Q: Can I search cantonal company data in one run?
A: Yes. That is one of the main reasons to use this actor, especially because Swiss company data is distributed across cantonal sources.

Q: Can I export the results?
A: Yes. Apify datasets can be exported in formats like JSON, CSV, Excel, XML, and RSS.

Q: Is this only for developers?
A: No. It can be run directly in Apify with form inputs, and the developer-oriented examples are tucked into collapsible sections.

---

Related Actors

If you are building a broader European public-data workflow, these may also fit:

Need	Actor
France public-sector data	France Government Data Search
Denmark public-sector data	Denmark Government Data Search
EU business and company registries	EU Business Data Search
Global company registries	Global Company Search

More actors: apify.com/lentic_clockss

---

Also Available

• Direct API: https://opendata.best/api/v1/data
• Postman collection: Fork and test
• GitHub: Collection source files