# Switzerland Company Registry (Zefix) Fresh Details (`vhsgreed/switzerland-zefix-api-fresh`) Actor

Official Swiss Zefix central business register data. Search by name or fetch registry IDs (ehraid / CHE-UID) directly: legal form, status, canton, seat, purpose, SHAB publications. No scraping, no API key.

- **URL**: https://apify.com/vhsgreed/switzerland-zefix-api-fresh.md
- **Developed by:** [Karl Sundström](https://apify.com/vhsgreed) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.95 / 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

## Switzerland Company Registry (Zefix) — Swiss Company Data API

> Independent tool, not affiliated with the Swiss commercial register (Zefix / Handelsregister).

Extract **official Swiss company data from Zefix**, the central business name index of the Swiss commercial register. Search by name or fetch registry IDs (ehraid / CHE-UID) directly. Get legal form, status, canton, seat, corporate purpose, SHAB publications and cantonal excerpt links. Official public API — no scraping of gated services, no API key.

### Why Zefix Registry API?

- ✅ **Verify Swiss counterparties** — legal form, status and seat straight from the central register.
- 🇨🇭 **Canton-level precision** — canton, seat and register office on every record.
- 📰 **SHAB publications** — the latest official gazette entries (up to 5) via `fetchDetails`.
- 🎯 **Two search modes** — exact registered-name match or keyword (`inexact`).
- 📋 **Compliance-ready output** — flat, one-record-per-company JSON for KYC automation.

### Use cases

KYC/counterparty verification in Switzerland · due diligence with SHAB gazette context · market mapping by canton and legal form · CRM enrichment

### What data you get?

| 🏷️ Field | Description |
| --- | --- |
| 🆔 ehraid / uid / chid | Zefix registry ID, CHE-UID, CHID |
| 🏢 name | Company name |
| 📍 legalSeat / canton / registerOffice | Seat, canton, register office |
| 🏛️ legalForm / legalFormShort | Legal form |
| ✅ status / registryStatus | Status (active/deleted/other) + raw status |
| 📅 deleteDate / lastShabDate | Deletion and last SHAB publication dates |
| 🔗 cantonalExcerptUrl | Cantonal excerpt link |
| 🎯 purpose | Corporate purpose (via fetchDetails) |
| 📰 shabPublications | SHAB gazette entries (up to 5, via fetchDetails) |

### How to use

1. Add the actor to your Apify account and click **Run**.
2. Enter `query` (e.g. `Coop`) with `searchType` (`exact` default, or `inexact` for keywords), or an `ehraidList`.
3. Enable `fetchDetails` for purpose and SHAB publications.
4. Set `maxResults` to cap the run (default 100, max 1000).
5. Export results as JSON, CSV or Excel.

### Input

```json
{
  "query": "Coop",
  "searchType": "exact",
  "fetchDetails": true
}
```

| Field | Type | Description | Default |
| --- | --- | --- | --- |
| `query` | string | Name searched in the official Zefix registry | — |
| `searchType` | enum | `exact` = full registered name match; `inexact` = keyword match | exact |
| `ehraidList` | array | Direct list of ehraid IDs or CHE-UID numbers (e.g. `364304` or `CHE-102.797.415`) | — |
| `fetchDetails` | boolean | Also fetch the full record (purpose, SHAB publications) | — |
| `maxResults` | integer | Cap on companies returned | 100 (max 1000) |

### Output

```json
{
  "ehraid": 364304,
  "uid": "CHE-102.797.415",
  "name": "Example AG",
  "legalSeat": "Zürich",
  "canton": "ZH",
  "legalForm": "Aktiengesellschaft",
  "legalFormShort": "AG",
  "status": "ACTIVE",
  "lastShabDate": "2026-06-30",
  "purpose": "Zweck der Gesellschaft ist…"
}
```

Purpose and SHAB publications appear only when `fetchDetails` is enabled and the register publishes them. Share capital is not published via the public API.

### Support

Questions or missing fields? Open an issue on the actor page or contact the developer via Apify.

# Actor input Schema

## `query` (type: `string`):

Name searched in the official Zefix registry, e.g. 'Coop' or 'Genossenschaft'

## `searchType` (type: `string`):

exact = full registered name match; inexact = keyword match (default exact)

## `ehraidList` (type: `array`):

Direct list of Zefix ehraid registry IDs or CHE-UID numbers (e.g. '364304' or 'CHE-102.797.120')

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

For each search result, also fetch the full record (purpose, SHAB publications)

## `maxResults` (type: `integer`):

Cap on companies returned (default 100, max 1000)

## Actor input object example

```json
{}
```

# Actor output Schema

## `companies` (type: `string`):

Dataset of Swiss company records (one per registry ID).

## `companiesJson` (type: `string`):

Full dataset items as raw JSON.

## `runStats` (type: `string`):

Key-value store entry OUTPUT\_STATS: pushed item count, query, and registry ID count for this run.

## `runView` (type: `string`):

Inspect this run, its logs and storages in Apify Console.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("vhsgreed/switzerland-zefix-api-fresh").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("vhsgreed/switzerland-zefix-api-fresh").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 '{}' |
apify call vhsgreed/switzerland-zefix-api-fresh --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,vhsgreed/switzerland-zefix-api-fresh"
        }
    }
}

```

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/mLMsWfQeefXiP4n43/builds/ediAdRc2zdP74hGeD/openapi.json