Skip to main content

Getting started

If you want to add electronic signing to your own system, the Swisscom Sign Integration API gives you a backend-first flow to create, configure, release, and monitor signing processes.

This guide follows the same path as the Swisscom reference documentation: understand the lifecycle, choose an integration style, authenticate with OAuth2, and test against the sandbox before going live. Before going to production, review the terms and conditions.

Ways to integrate​

There are two common integration models:

  1. Use your customer's own credentials. In this model, users subscribe and manage access for their own organization.
  2. Use your platform credentials. In this model, your application offers signing as part of your own product and handles the API access centrally.

For advanced setups such as custom domains, custom certificates, encryption material, or SSO, Swisscom expects a dedicated onboarding process.

Typical integration flow​

  1. Create a process with POST /api/process.
  2. Attach one or more PDF documents.
  3. Either release the process directly or hand it over to the setup UI.
  4. Open the signing flow for a specific signer if you need a deep link.
  5. Poll the status endpoint until the process completes.
  6. Download the final document and audit record.

See Concepts for the full lifecycle and endpoint reference.

Use the API explorer​

The API explorer tab loads the live OpenAPI contract directly from Swisscom and gives you an interactive REST client for authentication, request payload inspection, and endpoint testing.