Skribble API Overview
The Skribble API lets you integrate legally binding electronic signatures directly into your applications, workflows, and systems — whether you're automating contract signing, digitizing HR processes, or building compliance tooling.
Available APIs
Sign API v2
Stable — The current stable version of the signing API, recommended for all production integrations. Backward compatible with v1 — existing v1 integrations continue to work without changes.
Sign API v3
Sign API v3 is a preview release. The API surface may change before general availability. Do not use it in production without accepting that breaking changes may occur.
The next-generation signing API currently in preview. Key features:
- Draft workflow - Create signature requests in DRAFT status before initiating
- Multi-document support - Up to 50 documents per signature request
- Flexible signer management - Add/remove signers, support for signers without Skribble accounts
- Multiple signature qualities - SES, AES, and QES signatures
- Compliance - Supports both Swiss (ZertES) and EU (eIDAS) legislation
Validation API v1
Validate digitally signed documents and certificates:
- Document validation - Verify PDF and XML signatures
- Signature validation - Validate CMS/CAdES signatures independently
- Validation reports - Generate ETSI TS 119 102-2 compliant reports
- PDF processing - Convert, conform to PDF/A, and compress documents
Environment Overview
| Environment | Purpose | API Key Prefix |
|---|---|---|
| Demo | Testing and development | api_demo |
| Production | Live transactions (billable) | api_production or api_prod |
Quick Start
- Get API credentials - Generate your API username and key in the Admin UI
- Authenticate - Call
/access/loginto obtain a JWT token - First document to get signed - Create and submit your first signature request using the Sign API v2
- Handle responses - Process results and implement appropriate error handling
Support
For questions or support, reach us at info@skribble.com.