If it speaks HTTP, it signs
We won’t show you a wall of 300 logos where most are one vendor’s connectors in a trench coat. DrakonSign integrates the durable way: a clean REST API, a machine-readable spec, and evidence you can pull into any system you already run.
Three doors in
The REST API
Every envelope operation — upload, place fields, send, track and download evidence — behind one X-API-Key header. Billing, API-key management and account security remain session-only. Included on every plan.
The OpenAPI spec
/openapi.json is generated from the running service. Feed it to a client generator for typed SDKs in your language, or browse it live at /docs.
AI agents
An API an agent can drive was the design goal, not an afterthought — hand /openapi.json to Claude or any tool-using agent and it has everything it needs.
Recipes that work today
Each of these is wired with plain HTTP calls — the endpoints are listed so your developer (or your agent) can start from this page.
Your own product or back office
Generate a contract, send it for signature and file the evidence without a human touching the dashboard. This is how Drakon sends its own tenancy packs.
POST /api/documentsPOST …/signersPOST …/ai/suggest-fieldsPATCH …/fields/{id}POST …/send
Your CRM
Deal moves to “agreed” — your CRM automation creates the envelope and sends it, then polls status and stamps the deal when everyone has signed.
POST /api/documentsPOST …/sendGET /api/documents/{id}
Your document archive
On completion, pull the completed signed PDF, the certificate and the audit trail into your DMS or case-management system — including the seal state measured and recorded for that completion.
GET …/downloadGET …/certificateGET …/auditGET …/anchor
AI agents
Point an agent at the OpenAPI spec and it can prepare, send and track envelopes with natural-language instructions. Drakon's own onboarding agent sends real tenancy packs this way. The intelligence is in your agent; the endpoints it drives are ordinary REST.
GET /openapi.json…then any of the above
Signed outbound webhooks
Register an HTTPS destination in Account → Webhooks and we POST a signed JSON body when an envelope is viewed, completed, declined or voided — so your systems stop polling. Owner-only, and deliberately not something an API key can configure: a destination decides where every envelope event in your workspace goes.
Signed, and verifiable in six lines
HMAC-SHA256 over a timestamp and the exact body bytes, in X-DrakonSign-Signature. The secret is shown once, encrypted at rest, and rotatable. Working Python and Node examples are in the developer docs.
At-least-once, said plainly
We do not claim exactly-once — nothing over a network can. A delivery can arrive twice after a lost response, always with the same delivery id and the byte-identical body, so deduplicating on the event id is all your receiver needs.
Queued with the event, not after it
The delivery is written in the same database transaction as the signature or the cancellation it describes. If our process dies a millisecond later, the event is still owed and still goes out. Retries back off with jitter, cap at 24 hours, and a delivery log shows exactly what we sent and what you answered.
Minimal by design
The body carries identifiers, status, counts and links — never a signer’s name or address, never the document title, never field values or content. The detail is one authenticated API call away, where the caller proves who they are.
The first integration was ours
DrakonSign’s first customer is Drakon: our serviced-office tenancy packs are prepared and sent by an automated workflow calling this same public API with an ordinary org key — no private endpoints, no special access. If the API can’t do something, we feel it before you do.
Coming, not claimed
No-code connectors
RoadmapZapier-style connectors are planned. Until then, if a page on this site doesn’t say a connector exists — it doesn’t.
Per-organisation branding
RoadmapYour logo and colours on the signing page and the completion emails. Not in the product today.
Wire it up on the free trial
Checkout creates your workspace and sends a single-use magic sign-in link, not an API key. Sign in, create a revocable key from Account → API keys, and use the three trial envelope allowances to validate an integration end to end.