Rutba Sign API
Early accessElectronic signature API
Signing as an endpoint. Evidence as the response.
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.
Who it's for
- 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
What you get
- 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
Attaches as
Your own instance, or the shared service
What setting it up means
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.
Sold on its own too: Rutba Sign API has a site of its own at sign.rutba.io — the API reference, the live platform catalogue, and sign-up for the standalone product. Buying it there and buying it here get you the same service.
Worth knowing: Two backends, and the split is worth understanding before you build against it. The signing engine is a module inside a consumer instance - yours if you are licensed, a shared one otherwise - and it is where envelopes are created, sent and sealed. The public surface is served by the platform: verification, the key set, abuse reporting. That is why a counterparty verifying your document never touches your systems and never needs anything from you, and why verification is free and stays free. The envelope rate is identical to the application tier of Rutba Sign, because it is the same metered envelope arriving through a different door.
What Rutba Sign API costs
Free to start· 4 plans
Usage-based, so it scales with what you actually send, store, or publish.
Prices shown are indicative starting points while our plans are being finalised, and exclude local taxes. Your final quote is confirmed in writing before anything is charged.
Ready to try Rutba Sign API?
Start on the free tier, or talk to us about volume.