Send for signature from your own systems
Your CRM, HR system or property platform can send a contract the moment a deal closes, and hear the moment it is signed — with the same sealed documents, audit trail and certificate as everything sent from the app.
Read the API reference Getting started guide API or webhooks? Try bothA REST API over everything that matters
Create envelopes from your templates, filling in roles and variables, or from your own PDFs with fields placed by coordinates. Send, void, remind and resend. Follow each recipient's progress, and download the sealed documents, the combined PDF and the certificate of completion. Retries are safe: creating and sending take an Idempotency-Key, so a timeout never becomes a second contract.
A Word document in POST /envelopes becomes a PDF as the envelope is made, with its fonts embedded (Calibri drawn in Carlito, the same widths), comments removed and pictures or links to other places unlinked; one with tracked changes is refused with a 422 that says so. A file past the size limits, or one that isn't a Word file inside, is converted the simpler way instead, never refused. Only the PDF is kept.
Webhooks, signed so you can trust them
Choose the events you want — sent, viewed (once per recipient, the first time they open it), signed, completed, declined, expired, voided, and an email that bounced — and we POST each one to your HTTPS endpoint, signed with a secret only you hold, with a timestamp so a recorded delivery can't be replayed. A delivery your endpoint doesn't accept is retried for about three days, and every attempt is in a delivery log you can resend from.
Keys that do only what you allow
Each API key has the scopes you give it — read envelopes, send them, read templates, download documents, manage webhooks — and an optional expiry. You can change either, or its name, at any time, and a key you delete stops working on its next request. Keys are shown once and stored only as a hash. A key acts as the owner or admin who made it, so every envelope has a real sender, and it stops working if they leave.
On the record, like everything else
Every action taken through the API is on the envelope's tamper-evident audit trail, naming the person and the key it was made with. Making, changing and deleting keys and changing webhooks is on your workspace's activity log.
Embedded signing for people in front of you
For a customer signing at your counter or inside your own app, the API hands you a fresh signing link for that in-person signer, which replaces any link issued before it. People signing from an email keep their link to themselves — that link is the proof it was them.
How it fits together
Make a key in Settings → API & webhooks (the getting started guide walks through it), send Authorization: Bearer ssk_live_…, and call POST /api/v1/envelopes. Register a webhook endpoint in the same place and verify each delivery's SignSwifly-Signature header — the reference has the code to do it in C# and JavaScript. Errors are standard problem details with a code you can branch on, and each key may make 600 requests a minute.
The API and webhooks come with every paid plan, from Solo up. An envelope sent through the API counts as a signing session, like one sent from the app. Drafts cost nothing, so you can try the API and webhooks on drafts and envelopes to yourself. Read the getting started guide, or see plans.
Build it into your workflow
The full reference, with every request and response, is public.
Open the API reference