# Versions

Skribble's Sign API has three versions. v2 is the current stable version recommended for all production integrations. v3 is available as a preview — try it in non-production environments and share your feedback.

For how Skribble versions its APIs in general — what counts as a breaking vs. additive change, and how long previous versions are supported — see [Versioning](/api-versioning).

:::note{title="API v1 End of Support"}

Sign API v1 reached end of support on **30 November 2025**. After this date, v1 remains functional but breaking changes may be introduced without notice. If you are still on v1, upgrade to v2.

:::

## At a Glance

| | Sign API v2 | Sign API v3 |
|---------|:-----------:|:-----------:|
| Released | 25 June 2024 | Preview |
| Single-document requests | ✅ | ✅ |
| Multi-document requests (up to 50) | ❌ | ✅ |
| Draft signature requests | ❌ | ✅ |
| Signer groups | ❌ | ✅ |
| Observer groups | ❌ | ✅ |
| SES / AES / QES signature qualities | ✅ | ✅ |
| Express QES (xQES) | ✅ | ✅ |
| ZertES and eIDAS compliance | ✅ | ✅ |
| Signature reminders | ✅ | ✅ |
| Attachments | ✅ | ✅ |

## What's New in v3

### Multi-Document Requests

A single signature request can contain **up to 50 documents**. All documents are signed together in one flow, which reduces friction for complex processes that would otherwise require multiple separate requests.

### Draft Workflow

Signature requests can be created in `DRAFT` status and fully configured before being initiated. This lets you assemble documents, add signers, and set options across multiple API calls before committing — no more needing to get everything right in a single create call.

### Express QES (xQES)

Both v2 and v3 support **Express QES** — a streamlined qualified electronic signature flow with identification-related endpoints that allow signers to complete the QES process without leaving your application.

### Signer and Observer Groups

v3 introduces **groups** for both signers and observers:

- **Signer groups** — define parallel or sequential signing workflows. Signers in the same group can sign in any order; groups are completed sequentially.
- **Observer groups** — grant stakeholders read-only access to the request and its documents without being part of the signing flow.

## Base URLs

Skribble hosts data in two regions. Choose the region that matches your data residency requirements and use it consistently across all API calls.

| Region | Sign API v2 | Sign API v3 |
|--------|-------------|-------------|
| **Switzerland (CH)** | `https://api.skribble.com/v2` | `https://api.skribble.com/v3` |
| **Germany (DE)** | `https://api.skribble.de/v2` | `https://api.skribble.de/v3` |

## Migrating from v2 to v3

v3 is not a drop-in replacement for v2 — the signing flow has an extra step and several field shapes have changed.

[→ Migration guide](/api/sign-v3/migrate-from-v2)