Rutba Sign API Early access
Create an envelope, send it, and collect a sealed, hash-chained record of the whole ceremony — over a REST API with scoped keys, signed webhooks and a typed SDK, plus a public verification surface that needs no key at all.
Why Rutba Sign API
Every signature API returns a signed document and an audit report the vendor vouches for, which is worth exactly as much as your relationship with that vendor. This one returns a record anyone can check independently: the documents pinned by hash, the events chained, the completion manifest sealed and timestamped by a public authority. Your counterparty verifies it by calling a public endpoint with no key and no account — and the call does not touch your systems, so it keeps working whether or not your instance is up.
Product teams embedding signature into their own application
Businesses whose agreements are generated by software rather than typed by a person
Anyone who needs a counterparty to verify a document without an account or a key
Integrators replacing a signature vendor without replacing the surrounding workflow
The apps Rutba Sign API unlocks
One listing, 3 applications — all on the same customer record, catalog and books as the rest of the family.
Signing API
The authenticated surface — envelopes, templates and the sealed result at /api/sign/v1, with sgk_ bearer keys and signed webhooks. Runs inside your own instance, beside the documents it signs.
Public verification surface
Verification by digest — a sealed record's, or a single party's receipt, countersigned the moment they acted — the published key set and abuse reporting, served by the platform rather than by your instance; so a counterparty checks a document without a key, without an account, and without reaching your systems. Behind the same platform, the formality desk that arranges a stamp, seal or notarisation your sender asked Rutba for.
SDK
A typed client generated from the same routes the engine serves, so a change to the API is a compile error rather than a support ticket.
What you can do with it
- REST API with scoped, revocable bearer keys
- Signed webhooks on every envelope event
- A typed SDK generated from the routes themselves
- Templates and bulk send through the same API
- Public verification by digest — no key, no account, permanent
- The published key set, so a seal can be checked without asking us
- The identity ladder chosen per signer: email, phone code, access code, location
- Each party's receipt countersigned by the platform the instant they act — proof they hold before the envelope seals
- The agreement lifecycle through the same API: compose in one call, calendars, renewals, formalities with their stages
Pricing
Indicative pricing as published on rutba.io, where subscriptions are managed and billed. Talk to us for volume, migration or on-premise terms.
What you get on signup — On a Rutba licence the engine runs inside your own instance, beside your documents, and keys are minted there. Without one it runs on the shared service — which waits on card capture and pooled hosting.
Free
$0 verification, unlimited
The public half, which never costs anything.
- Verify any completed package by digest
- Fetch the published key set
- No account, no key, no rate card
- Permanent — it keeps working after you stop paying for anything else
Standard
$0.90 per envelope sent
Send from code, with no seat count and no monthly minimum.
- The same rate the application charges — one envelope, one price
- Charged when an envelope is sent, not when it completes
- Scoped API keys and signed webhooks
- Templates and bulk send
- The complete evidence record, the evidence pack, and per-act receipts
Scale
$249 per month, 400 envelopes
A commitment that earns a lower rate, for volume senders.
- 400 envelopes a month included — an effective $0.62 each
- $0.70 per envelope beyond them, not a penalty band
- Higher rate limits
- Webhook delivery retries with a dead-letter view
- Priority support
Enterprise
Custom annual contract
Volume, residency and the paperwork that comes with both.
- Committed volume pricing
- Data residency options
- A dedicated instance rather than the shared service
- Named support and an SLA
See Rutba Sign API in your business
Buy it on rutba.io, or talk to the team that builds and runs it. Works well with Rutba Sign, Rutba Drive, Rutba CRM.