Changelog

10 September 2026 (v1.54.43)

An unknown UID, or a UID the register rejects, returns HTTP 404 with Entity not found on lookup by UID. The same lookup previously returned HTTP 500. A deleted or struck-off company is not a 404: the UID still exists. See 6 August and Common Status Codes.
Suggestions accepts a UID such as CHE-123.456.789. A UID that was not found used to return HTTP 404. The call now continues with a name search to confirm that this UID does not exist. If that search also finds nothing, the response is HTTP 200 and an empty list.
Signing rules and validation return fewer false RULES_SIGNATORY_MISMATCH errors. Members of a management or executive board (Geschäftsleitung, direction générale, or direzione generale) are now consistently classified as MANAGING_DIRECTOR. A signatory that still cannot be classified still returns HTTP 500 with errorCode: RULES_SIGNATORY_MISMATCH. See 27 August.

requiredRoles lists role codes that at least one other signer must hold. A signer cannot satisfy this with their own role. SIGNER_MISSING_REQUIRED_ROLE is no longer returned; use MISSING_REQUIRED_ROLE, and accept the role code VICE_PRESIDENT. For example, CHE-108.954.576 has a collective signature that requires the other signer to be the president or the vice-president, so requiredRoles is PRESIDENT and VICE_PRESIDENT. That signer is rejected unless the other signer holds one of those roles. See Validate signatories.
signingCompetence.mode can be LIMITED_JOINT as well as JOINT, INDIVIDUAL, and NONE. LIMITED_JOINT is a collective power of attorney (Kollektivprokura). Validation can still be isValid: true, and the response then includes hints with code LIMITED_JOINT_SIGNERS because a monetary limit may apply. CHE-103.856.179 is an example. See Validate signatories.
If a signatory with signing authority cannot be classified, Get signing rules and Validate signatories return HTTP 500 with errorCode: RULES_SIGNATORY_MISMATCH. Previously those calls returned HTTP 200 and left that signatory out. Treat this as incomplete rules. Retrying will not succeed.

List signatories returns HTTP 200 and signatories: [] only when the cantonal commercial-register page lists nobody. The organisation was found. This is common for branches, such as CHE-307.343.483, and also happens for some companies in liquidation, such as CHE-102.314.645. HTTP 500 means that cantonal page could not be read, so the call does not say whether anyone can sign.
An empty list does not mean the company was deleted, and a deleted company is not a 404. The list is whoever the cantonal commercial-register page still names. CHE-100.583.743 is deleted and still has signatories. Get ZEFIX excerpt for deleted companies that previously failed with HTTP 500 now returns the cantonal excerpt.

A collective signature can require the other signer to belong to a named group. The group is the letter in the role, such as (a). For CHE-114.630.047, signing rules show requiredGroups of a on the collective signers who need that group, and groups of a on the members of the group. Validation still returns HTTP 200. Two collective signers are isValid: false with failureCode: MISSING_REQUIRED_GROUP when neither belongs to group a. The same collective signer together with a member of group a is valid. invalidSigners lists only the signers whose group is still missing.
Signing rules no longer omit signatories when the register writes the same signing competence with different spacing or a footnote marker. This changes only previously incomplete rule results; no client change is required.

Production feature-flag enablement, not a new merge to main. The build version is from the preceding 4 June merge.

creationDate was added to the signatories response and enabled in production. No change is required if you ignore fields you do not use.

?includeTranslations=true on lookup by UID and lookup by exact legal name adds language-classified names. Omit it and the response stays as before.
Lookup by exact legal name matches names that differ only by extra spaces.

Organisation lookups include additionalNames when the registry has alternate or trade names. The field is omitted when there are none. See Lookup by UID.
?includeParsedParams=true on list signatories and signing rules adds parsedParams and roleI18n. Omit it and those fields stay out of the response.
List signatories ignores unknown query parameters. An old parameter such as rawResult does not fail the request.
List signatories, signing rules, validation, and Get ZEFIX excerpt return HTTP 404 when ZEFIX has no company for the UID. They do not fall back to the UID register. Lookup by UID still uses the UID register.