March 2026

SSO for process release

A user is already authenticated in the corporate customer portal and starts a signing process there. When they click the signing link, they are taken straight to the document without having to provide an additional delivery via SMS or email, because they are already identified.

Integration: In the Sign API, process authentication via SSO is controlled with the authorization parameter of the POST /api/process endpoint, using the value ACCOUNT.

Related API version: 2.7.0

List processes

Using the new GET /api/process endpoint, customer systems can read all of their processes. The response is a paginated list that can be filtered by process status (CREATED, PENDING, COMPLETED, EXPIRED).

Related API version: 2.11.0

Signer validation

After signing, the Sign API compares the name of the invited signer with the name in that signer's certificate and exposes the validation result per signer via the GET /api/process/{processId} endpoint in the certificateMatch field. The possible values are UNCHECKED, MATCH, MISMATCH. The feature can be used to streamline the downstream manual validation: documents with status MATCH no longer require a manual re-check for this match.

Related API field: certificateMatch

Assign a process to a team

The POST /api/process endpoint has a new teamId parameter to control the assignment. In the UI, the process then appears under the processes of the respective team.

Related API version: 2.9.0

Partner ID

The partner ID is issued for Swisscom partners and set in the POST /api/process endpoint via the optional partnerId field. This allows a partner's processes to be attributed.

Related API version: 2.8.0