Concepts

Process lifecycle

A signing process moves through four states:

State	Meaning
CREATED	The process exists and files can still be attached.
PENDING	The process was released and is waiting for signatures.
COMPLETED	All required signatures were collected.
EXPIRED	The process did not complete before expiry.

Core services

Create and prepare

Method	Endpoint	Minimum state	Purpose
POST	/api/process	-	Create a new signing process.
POST	/api/process/{processId}/attach	CREATED	Attach a PDF document.
POST	/api/process/{processId}/setup	CREATED	Hand the process to the Swisscom UI for manual setup.
POST	/api/process/{processId}/release	CREATED	Release a fully prepared process without manual UI interaction.
POST	/api/process/{processId}/open/{personId}	PENDING	Generate a signer-specific URL for direct access.

Read and monitor

Method	Endpoint	Minimum state	Purpose
GET	/api/process/{processId}	CREATED	Retrieve the full process payload.
GET	/api/process/{processId}/status	CREATED	Read the current lifecycle state.
GET	/api/process/{processId}/file/{fileId}	CREATED / COMPLETED	Download originals or signed output.
GET	/api/process/{processId}/record	CREATED	Fetch the audit record trail.

Process authorization

Swisscom distinguishes between initiators and invitees when deciding whether a person may access a process.

For initiators, access is first resolved through direct ownership, then organization or team membership, and then verified contact attributes such as email address or mobile number. If none of those checks applies, the platform falls back to a one-time code flow.

For invitees, the normal path is a verified email or mobile number match, with the same code-based fallback if no verified attribute can be used.