Open Company Data in Switzerland: Official Sources, APIs and Reuse Rights

Switzerland is one of the cleaner European-quality company-data markets, but it still needs careful framing. The strongest official route is not a generic directory; it is a stack of official systems: Zefix REST for central company lookup, UID for enterprise identifiers, SOGC/SHAB for official commercial notices, opendata.swiss for dataset discovery and terms, SIMAP for procurement, FINMA for regulated financial institutions, Swissreg for IP ownership, COMCO for competition context and GLEIF for LEI records.

The safe editorial claim is that Switzerland has strong official search, API and identifier infrastructure. The unsafe claim would be that every cantonal register document, natural-person detail, beneficial-ownership signal, procurement contact or regulator publication can be reused as a complete free marketing database. A credible article has to separate company identity from documents, notices, enrichment layers and contact-data use.

This Wave 30 refresh updates the live Switzerland page into a deeper reference article. It maps the official sources, explains search/API/bulk options, records reuse limits and shows where CompaniesData adds practical value by turning fragmented official sources into a normalized, provenance-aware business dataset.

Key Takeaways

• Best technical backbone: Zefix REST is the central official machine-access route for company lookup and commercial-register context.
• Best identifier layer: UID helps normalize Swiss entities across registry, statistical, procurement, regulator and LEI data.
• Best legal-publication layer: SOGC/SHAB is essential for commercial-register events and official notices, but it is not a current master database by itself.
• Best enrichment layers: SIMAP, FINMA, Swissreg, COMCO and GLEIF support procurement, regulated-entity, IP, competition and KYB workflows.
• Main caution: Federal/cantonal boundary, document reuse, natural-person data and marketing-contact use require separate controls.

Editorial Methodology

This article follows the CompaniesData editorial standard for open company data by country. It starts with official registry and identifier sources, then adds official legal publication, open-data, statistics, procurement, regulator, IP, competition and LEI layers. Private contact-data vendors are not used as evidence for official company-data reuse rights.

Every final linked source was checked from this environment on 2026-05-29. Sources returning hard 404 or 410 are excluded. Sources with stale routes or legal uncertainty are documented as held-source notes. Logos in the source matrix and Resource Pack are decorative favicon cues only; the evidence remains the official URL, owner, access model and reuse note.

Coverage, Access and Update-Risk Analysis

Switzerland company-data coverage should be described as a federal/cantonal source stack. Zefix centralizes the business-name index and provides REST access, but underlying commercial-register authority and document products still require source-specific care. UID gives an identifier layer. SOGC/SHAB publishes legal events. The open-data and statistical layers help with reuse and benchmarking, while procurement, regulator, IP, competition and LEI sources add enrichment for known entities.

Federal/cantonal boundary: a normalized Swiss company profile should preserve where each fact came from. A Zefix search result, UID record, SOGC notice, Swissreg IP record and FINMA list entry can refer to the same organization, but they are not the same source and do not carry the same reuse rights.

Zefix API boundary: Zefix REST is strong evidence for official technical access. It does not automatically make every source document, historical extract or personal field an unrestricted bulk product. Bulk ingestion should preserve source terms, query date, endpoint, field list and any restrictions attached to downstream documents.

Update risk: Zefix, UID, SOGC/SHAB, opendata.swiss, SIMAP, FINMA, Swissreg, COMCO and GLEIF update on different schedules. A practical dataset needs source-level timestamps and stale-record detection rather than a single generic “updated” flag.

Reuse Checklist

• Confirm the source owner: distinguish Federal Office of Justice, Federal Statistical Office, SECO/SOGC, opendata.swiss, SIMAP, FINMA, IPI/Swissreg, COMCO and GLEIF.
• Separate search from reuse: public search and API access do not automatically permit unrestricted redistribution of every field or document.
• Preserve attribution and no-endorsement language: where open-data terms apply, keep source and update metadata visible.
• Flag federal/cantonal scope: do not flatten cantonal register facts into a generic national assertion without provenance.
• Protect natural-person fields: directors, signatories, addresses and beneficial-ownership-adjacent details need privacy and lawful-use review.
• Label enrichment layers: procurement, regulator, IP, competition and LEI sources are useful subsets, not full company coverage.
• Block contact-data shortcuts: registry visibility is not consent for email lists, phone lists or sales-prospecting campaigns. English/international contact-data demand should route to CompaniesData.cloud; Spanish-speaking or Hispanic contexts should route to CentraldeComunicacion.es.

Practical Source Workflow

1. Start with Zefix: use the REST API or official lookup route to identify the Swiss entity and core registry context.
2. Normalize with UID: store UID where available and use it as an identifier bridge across sources.
3. Check SOGC/SHAB: add commercial-register notices for event history and legal traceability.
4. Check open-data terms: use opendata.swiss dataset pages and terms before making reuse or bulk claims.
5. Add public-sector activity: use SIMAP for procurement, with supplier/tender scope clearly marked.
6. Add risk and sector context: use FINMA for regulated financial entities and COMCO for competition or market-conduct context.
7. Add IP and LEI evidence: use Swissreg and GLEIF for trademarks, patents, designs and legal-entity identifiers, then match carefully back to the registry identity.
8. Keep contact data separate: do not convert official registry visibility into marketing permission without separate lawful-basis, suppression and outreach controls.

Source-Risk Findings

Switzerland passes the Wave 30 refresh bar as a strong official API/search/reference article. The final linked source set has no hard 404/410 failures and no controlled-source warnings in the source live check. The article avoids the old unsupported wording that treated Switzerland as a broad open bulk register market.

Held source-risk findings: the stale SME commercial-register route without encoded space is not linked as a public source. Cantonal extract/document products and beneficial-ownership or natural-person detail claims remain manual-review issues. They should not be used as ordinary open-bulk or marketing-contact evidence.

Claims allowed in this article

• Switzerland has strong official company lookup and API evidence through Zefix REST.
• UID helps normalize enterprise identifiers across sources.
• SOGC/SHAB is an official commercial-notice and legal-publication source.
• SIMAP, FINMA, Swissreg, COMCO and GLEIF are official or high-quality enrichment layers.
• CompaniesData adds value by preserving source provenance and normalizing across fragmented official layers.

Claims not allowed in this article

• Do not claim every Swiss company document is available as unrestricted free official bulk data.
• Do not describe legal notices as complete current company profiles.
• Do not treat regulator, procurement, IP or LEI records as all-company coverage.
• Do not imply that public registry data creates consent for marketing emails or phone outreach.
• Do not imply endorsement by Swiss authorities or GLEIF.

Source-by-Source Deep Dives

1. Zefix REST API

Authority: Federal Office of Justice / Swiss Confederation. Type: official registry API. Access model: REST API / Swagger. Reuse position: source terms and public-sector information caution.

Primary technical route for official company and commercial-register lookup across Switzerland. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Strong for lookup and monitoring, but document extracts, cantonal source records and downstream reuse still need field-level review. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

2. Zefix dataset on opendata.swiss

Authority: Swiss Confederation / opendata.swiss. Type: official open data. Access model: catalogue / dataset metadata / downloads where available. Reuse position: dataset-specific opendata.swiss terms.

Evidence that the central business name index is represented in Switzerland's official open-data catalogue. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: The article must cite the declared dataset terms and avoid assuming that every register document is open bulk data. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

3. UID Register

Authority: Federal Statistical Office. Type: identifier / official register. Access model: search / identifier services. Reuse position: source terms and personal-data caution.

Official enterprise-identification layer for normalizing Swiss entities across sources. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: UID is an identifier and verification layer, not a complete legal profile or marketing-contact dataset. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

4. SOGC / SHAB

Authority: State Secretariat for Economic Affairs. Type: legal publication / gazette. Access model: search / official commercial notices. Reuse position: source terms and notice-level context.

Official commercial-register event publications for changes, notices and legal traceability. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Gazette notices are event publications, not a complete current company master database. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

5. opendata.swiss terms of use

Authority: opendata.swiss. Type: official open-data terms. Access model: licence / terms page. Reuse position: open-data terms, attribution and dataset-specific conditions.

Reuse-rights reference for open Swiss public-sector datasets where the dataset declares compatible terms. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Terms apply source by source; they do not override registry, document, privacy or third-party restrictions. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

6. Federal Statistical Office

Authority: Federal Statistical Office. Type: official statistics. Access model: statistics / publications / datasets. Reuse position: BFS publication and data terms.

Business-demography and statistical context for benchmarking coverage and sector/geography distributions. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Aggregate/statistical information is not legal entity-level registry data. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

7. SIMAP

Authority: Swiss public procurement platform. Type: official procurement. Access model: portal / tenders / procurement notices. Reuse position: platform and notice-level terms.

Public procurement supplier, tender and award enrichment for known companies. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Procurement records cover public-sector transactions, not all Swiss companies. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

8. FINMA authorised institutions

Authority: Swiss Financial Market Supervisory Authority. Type: regulator / compliance. Access model: registers / lists / search. Reuse position: FINMA publication terms.

Financial-sector regulated-entity enrichment and compliance screening. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: FINMA scope is sector-specific and should not be treated as all-company coverage. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

9. Swissreg

Authority: Swiss Federal Institute of Intellectual Property. Type: official intellectual property. Access model: search / database. Reuse position: Swissreg and IPI terms.

Trademark, patent and design-owner enrichment for company profiles. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: IP records require entity matching and do not prove current company status by themselves. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

10. COMCO

Authority: Competition Commission. Type: competition regulator. Access model: decisions / publications / guidance. Reuse position: official publication terms and case-specific context.

Competition, merger and enforcement context for risk and market-conduct enrichment. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: Decision-based regulator source, not a registry-wide company database. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

11. GLEIF LEI records for Switzerland

Authority: GLEIF. Type: global legal-entity identifier data. Access model: API / open data. Reuse position: GLEIF API and open-data terms.

LEI cross-checks for Swiss legal entities in finance, KYB and compliance workflows. In a production dataset, this source should be stored with source owner, access date, language, jurisdiction scope, update cadence and field-level provenance. Switzerland is multilingual and federal/cantonal, so provenance is not optional: it is the control that prevents a Zefix lookup, a UID identifier, a SOGC notice and a regulator publication from being collapsed into one unsupported claim.

Limitations and operating notes: LEI coverage is limited to entities that have an LEI; it is not comprehensive registry coverage. Use this layer for the job it actually performs. Registry identity, legal notices, procurement signals, regulated-entity lists, IP ownership and LEI records answer different questions. CompaniesData normalization is valuable because it keeps those distinctions visible while still giving analysts a practical entity profile.

Recommended Data Model

A Swiss company-data model should be provenance-first. The minimum useful structure is not just name and address; it should preserve source, jurisdiction, identifier, update date, access model and lawful-use notes.

• Entity core: normalized legal name, alternative names, legal form, status, registered office and country.
• Identifiers: UID, Zefix or register references, LEI where available, source-native IDs and matching confidence.
• Source provenance: source URL, owner, access date, endpoint, language, licence/reuse note and update cadence.
• Event layer: SOGC/SHAB notices, registration changes, publication dates and event types.
• Activity/enrichment: SIMAP procurement records, Swissreg IP records, FINMA regulated-entity flags, COMCO decision references and GLEIF status.
• Risk flags: federal/cantonal boundary, document-reuse caution, natural-person field caution, stale-source warning and marketing-contact separation.
• Delivery fields: source package version, row checksum, transformation notes and suppression/compliance status for any contact-enrichment layer.

Missing-Data Gaps

• No single universal marketing file: the official source stack is not a consented email or phone database.
• Document access varies: register documents and extracts can carry separate access and reuse conditions.
• Federal/cantonal detail varies: national discovery does not remove the need to understand canton-level source context.
• Historical completeness varies by source: SOGC notices, Zefix records, regulator lists and LEIs have different historical depth.
• Language and transliteration matter: German, French, Italian and English labels can affect matching, deduplication and user search.
• Regulator and procurement sources are subsets: they help enrich known companies but cannot replace the registry backbone.

How CompaniesData Adds Value

For Switzerland, CompaniesData turns a strong but fragmented official ecosystem into a practical dataset. The value is not pretending that every portal is one bulk file. The value is source-aware normalization: matching Zefix and UID records, preserving SOGC event context, adding procurement, regulator, IP and LEI signals, and keeping contact-data use outside the official-source claim.

• Normalize identifiers: align legal names, UID values, Zefix references and LEIs where available.
• Deduplicate multilingual records: handle German, French, Italian and English labels without losing source provenance.
• Preserve auditability: every derived field should point back to source owner, URL, access date and reuse note.
• Add enrichment responsibly: procurement, IP, regulator, competition and LEI signals improve analysis only when their subset limitations are visible.
• Separate contact workflows: marketing outreach requires a separate compliant process, suppression logic and lawful-basis assessment.

Request a CompaniesData sample for Switzerland if you need a practical normalized dataset rather than a list of portals.

Manual, API and Bulk Options

Manual lookup

Manual users should start with Zefix and UID, then verify SOGC/SHAB notices if legal event history matters. Manual lookup is appropriate for due diligence on one company, but it is slow for market research or CRM preparation.

API route

The strongest technical route is Zefix REST. API projects should store endpoint, query, response date, field list and any restrictions attached to document or downstream source material. GLEIF also offers an API for LEI-covered entities, but LEI coverage is partial.

Open-data route

opendata.swiss can provide catalogue and reuse context, especially for datasets that explicitly declare open terms. The article should not generalize those terms to every registry document or every third-party source.

Commercial normalized route

A normalized CompaniesData-style workflow is appropriate when the user needs deduplication, source provenance, enrichment, consistent country fields, delivery formats and contact-data separation. That is different from scraping public pages or buying a raw lead list.

Source Matrix

Source	Owner / authority	Access model	Reuse note	Main limitation
Zefix REST API	Federal Office of Justice / Swiss Confederation	REST API / Swagger	source terms and public-sector information caution	Strong for lookup and monitoring, but document extracts, cantonal source records and downstream reuse still need field-level review.
Zefix dataset on opendata.swiss	Swiss Confederation / opendata.swiss	catalogue / dataset metadata / downloads where available	dataset-specific opendata.swiss terms	The article must cite the declared dataset terms and avoid assuming that every register document is open bulk data.
UID Register	Federal Statistical Office	search / identifier services	source terms and personal-data caution	UID is an identifier and verification layer, not a complete legal profile or marketing-contact dataset.
SOGC / SHAB	State Secretariat for Economic Affairs	search / official commercial notices	source terms and notice-level context	Gazette notices are event publications, not a complete current company master database.
opendata.swiss terms of use	opendata.swiss	licence / terms page	open-data terms, attribution and dataset-specific conditions	Terms apply source by source; they do not override registry, document, privacy or third-party restrictions.
Federal Statistical Office	Federal Statistical Office	statistics / publications / datasets	BFS publication and data terms	Aggregate/statistical information is not legal entity-level registry data.
SIMAP	Swiss public procurement platform	portal / tenders / procurement notices	platform and notice-level terms	Procurement records cover public-sector transactions, not all Swiss companies.
FINMA authorised institutions	Swiss Financial Market Supervisory Authority	registers / lists / search	FINMA publication terms	FINMA scope is sector-specific and should not be treated as all-company coverage.
Swissreg	Swiss Federal Institute of Intellectual Property	search / database	Swissreg and IPI terms	IP records require entity matching and do not prove current company status by themselves.
COMCO	Competition Commission	decisions / publications / guidance	official publication terms and case-specific context	Decision-based regulator source, not a registry-wide company database.
GLEIF LEI records for Switzerland	GLEIF	API / open data	GLEIF API and open-data terms	LEI coverage is limited to entities that have an LEI; it is not comprehensive registry coverage.

Resource Pack

Held Source-Risk Notes

• Commercial register SME portal deep link without encoded space: held because this clean-looking route returned 404; the article relies on Zefix REST, UID and SOGC/SHAB instead.
• Cantonal register extract/document products: held for source-specific/manual reuse review; document extracts and cantonal source records should not be described as unrestricted bulk data.
• Beneficial-ownership or natural-person detail claims: held as a normal publication claim unless a lawful public-access and reuse basis is documented for the specific source and field.

FAQ

Is there a single free official bulk company database for Switzerland?

No simple claim should be made. Switzerland has strong official lookup, API and identifier sources, especially Zefix REST and UID, but register documents, cantonal details, legal notices and enrichment layers can have separate access and reuse conditions.

What is the best first source for Swiss company data?

Start with Zefix REST or official Zefix lookup, then normalize with UID and add SOGC/SHAB notices where event history matters.

Can opendata.swiss be used for commercial reuse?

Often yes for datasets that declare compatible terms, but the exact dataset terms, attribution requirements, no-endorsement language and third-party rights still matter.

What does UID add?

UID gives a strong official identifier layer. It helps connect registry, statistics, procurement, regulator, IP and LEI data, but it is not a full company profile by itself.

Can SOGC/SHAB replace the company register?

No. SOGC/SHAB is a legal-publication and notice layer. It is valuable for events and traceability, but it is not a complete current company master file.

Are SIMAP suppliers the same as all Swiss companies?

No. SIMAP provides procurement activity and supplier context. It is useful enrichment for public-sector workflows, not all-company coverage.

Are FINMA and COMCO records company master data?

No. FINMA is a financial-regulator subset and COMCO is competition decision/enforcement context. Both are useful enrichment layers, not registry-wide coverage.

Can public registry data be used for cold email?

Not automatically. Contact-data use needs a separate lawful basis, suppression handling and marketing-compliance review. For international company-data projects, keep the official-source layer separate from contact enrichment through CompaniesData.cloud.

Why use CompaniesData instead of collecting Swiss sources manually?

Manual collection is slow because sources differ by authority, language, update cadence, identifier and reuse rules. CompaniesData adds normalization, matching, deduplication, provenance and delivery formats.

Official Sources

• Zefix REST API – official registry API
• Zefix dataset on opendata.swiss – official open data
• UID Register – identifier / official register
• SOGC / SHAB – legal publication / gazette
• opendata.swiss terms of use – official open-data terms
• Federal Statistical Office – official statistics
• SIMAP – official procurement
• FINMA authorised institutions – regulator / compliance
• Swissreg – official intellectual property
• COMCO – competition regulator
• GLEIF LEI records for Switzerland – global legal-entity identifier data