B2B Partner API Documentation

CheckName Partner API

Legiqo GmbH's partner API for integrating Swiss company name assessment and conflict checks into your own product, onboarding flow, or operations tooling. This is an enterprise B2B offering and not a self-service API.

Open quickstart Browse endpoints Assessment checks

For partner integrations

Built for SaaS platforms, legal-tech products, fiduciaries, onboarding systems, and internal review tools that need machine-readable company-name decisions.

Not the consumer app

This documentation covers the API integration surface. If you want the end-user search experience, use checkname.ch.

Enterprise onboarding

API access, pricing, and onboarding are handled individually by Legiqo. Contact contact@legiqo.com to discuss access and rollout.

Start here

Recommended reading path

1. Getting Started > Authentication
2. Getting Started > Quickstart
3. API Reference > Endpoints
4. API Reference > Assessment Checks and Codes
5. GET /v1/name/screening/catalog for screening code discovery

Base URLs

Environment	Base URL
Sandbox	https://api.test.checkname.ch
Production	https://api.checkname.ch

Integration summary

Primary endpoint: POST /v1/name/assessment
Bundled screening endpoint: POST /v1/name/screening Screening catalog endpoint: GET /v1/name/screening/catalog
Supporting endpoint: POST /v1/conflicts/search
Additional standalone screening endpoint: POST /v1/trademarks/search Authentication: X-API-Key
Canonical support identifier: traceId (X-Trace-Id mirrors the same value in the response headers) Important: HTTP 200 means the request executed successfully. Read top-level overallStatus for the business outcome.

Code-first UI handling

Treat code fields and enum values as the stable integration contract. API message fields are English fallback/debug copy only; render localized German UI text from your own copy map keyed by stable codes. Use GET /v1/name/screening/catalog to discover current screening issue codes, driver codes, statuses, and English descriptions.

For implementation teams

Start in Getting Started, then use API Reference for exact contracts, flags, and response semantics.

What this documentation covers

This site documents the B2B Partner API provided by Legiqo GmbH.

The API is offered as an enterprise partner service on an individual basis. It is not a public self-service API with instant signup or automated key issuance.

It is intended for teams embedding CheckName capabilities into their own systems, for example:

• customer onboarding journeys that collect a proposed Swiss company name
• partner platforms that want a rules-based decision before filing or handoff
• internal legal, compliance, or operations tools used by review teams
• assisted incorporation or registry-preparation workflows

It is not the consumer-facing CheckName product. The public product at checkname.ch is the end-user experience for one-off searches and risk assessments, while this API is the integration layer for partner applications and operational systems.

What this API is for

This partner API is designed for products and operations teams that need to evaluate proposed Swiss company names before they move further downstream.

Typical business use cases:

• onboarding flows where a customer enters a new company name
• internal review tools used by compliance, legal, or registry-support teams
• assisted filing experiences that need a fast decision signal before submission
• case management systems that route risky names to manual review

In practice, the API helps answer five different questions:

1. Is this proposed name likely acceptable from a company-name rules perspective?
2. What is the bundled screening outcome across assessment, company conflicts, trademarks, and optional domains?
3. Does the name appear to conflict with already registered Swiss companies?
4. Does the proposed brand/sign appear similar to registered trademarks?
5. Which exact issues should trigger warnings, review steps, or hard stops in your workflow?
6. Which stable response codes should your UI map to partner-controlled localized copy?

First successful request

1. Contact contact@legiqo.com for pricing, onboarding, and API key provisioning.
2. Call the primary assessment endpoint:

curl -X POST "https://api.test.checkname.ch/v1/name/assessment" \
  -H "X-API-Key: <your-api-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "companyName": "Alpen Data AG",
    "legalForm": "stock_corporation",
    "activityScope": "Software development services",
    "language": "de",
    "ownerSurname": null,
    "legalSeat": "Zurich",
    "languageVariants": [],
    "checkLevel": "full",
    "riskProfile": "balanced"
  }'

1. Confirm HTTP 200 and read business outcome from overallStatus.

How partners usually implement it

1. Call POST /v1/name/assessment as the primary decision endpoint.
2. Use overallStatus to decide whether to continue, warn, review, or block.
3. Read issues[].code to determine the exact reason and route the case correctly.
4. Use POST /v1/name/screening when you want one bundled response for assessment, company conflicts, trademark screening, and optional domain checks.
5. Use GET /v1/name/screening/catalog to retrieve the current list of screening codes/enums and English fallback descriptions.
6. Optionally call POST /v1/conflicts/search or POST /v1/trademarks/search directly when you want raw sub-check outputs or custom orchestration.
7. Persist traceId so support and operations teams can investigate individual requests later.

Deprecated endpoint

POST /v1/name/eligibility, POST /v2/name/eligibility, and POST /v3/name/eligibility are deprecated. Use POST /v1/name/assessment for new integrations and treat the eligibility endpoints as legacy migration-only APIs.

Need help?

• Contact contact@legiqo.com for API access, pricing, and onboarding.
• Use Operations > Status and SLA for uptime and availability commitments.
• Use Operations > Support for contact and escalation paths.
• Use Terms and Conditions for the general legal terms governing Legiqo services unless superseded by your partner agreement.