Signi API

Signi API connects your application — ERP, CRM, e-shop, or anything else — with Signi. Everything you would otherwise do manually in the app, your application can do on its own:

• send a document for signature — a ready-made file, or one generated from a template
• track the signing status — who has already signed and who hasn't
• download the signed PDF — including certificates and timestamps
• receive change notifications automatically (webhooks) — without repeated polling
• cancel and delete documents
• manage contacts and labels

How it works

Communication takes place via a REST API: ordinary secure web requests with data in JSON format. Every programming language can handle them, as well as tools like Postman or curl.

• Base address: https://api.signi.com
• Every request is authenticated with your workspace key in the x-api-key header

The whole principle has three steps:

1. Send a document (PDF, DOC…) and instructions — who signs and where the signature goes.
2. Signi contacts the signers by email and guides them through signing.
3. Download the signed PDF — or have yourself notified of completion automatically.

? Fastest start: Quickstart — your first document for signature in a few minutes

Directory

Introduction and basic concepts Introduction and basic concepts — overview — the basics before you start: terms for non-programmers, the API key, the document lifecycle, the JSON item by item, signing roles, webhooks, and error handling.

Typical tasks Typical tasks — overview — larger topics that almost every integration deals with: multiple signers, placing signatures, templates, attachments, downloading, deleting, contacts, and labels.

Examples Examples — overview — short demonstrations of individual features: signing order, autosign, certificate and Bank iD, delivery by legal fiction, notifications, metadata, and more.

Signi verification Signi verification — overview — verifying the counterparty's identity before signing (remote identification, AML): verification groups, linking to a document, approval, webhooks, and checklists.

Reference documentation Full description of all calls on SwaggerHub