/zefix/companies/search

POST /api/zefix/companies/search

Price: 5 credits

Search Swiss companies by name or UID

How to use it

Search the Swiss commercial register by company name or UID. Choose exact, containing or starting-with name matching, restrict to active or deleted companies, and pick the result language. Returns company summaries with EHRA ID, UID, legal seat and status.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• name string required — Company name or UID to search for (examples: "Nestle"; minLength: 1)
• count integer required — Max number of results (min: 1; max: 5000)
• search_type string — Name matching mode (default: "containing"; one of: "exact", "containing", "startingWith")
• language_key string — Result language (default: "en"; one of: "de", "fr", "it", "en")
• active_only boolean — Return only active (existing) companies (default: false)
• deleted_only boolean — Return only deleted companies (default: false)

Response

• @type string (default: "ZefixSearchCompany")
• ehraid integer nullable
• name string required
• uid string nullable
• uid_formatted string nullable
• chid string nullable
• chid_formatted string nullable
• legal_seat string nullable
• legal_seat_id integer nullable
• register_office_id integer nullable
• legal_form_id integer nullable
• status string nullable
• shab_date string nullable
• delete_date string nullable
• cantonal_excerpt_web string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.