Rutba Sign API: Product Datasheet

Signing as an endpoint. Evidence as the response.

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.

Family	Platform services
Category	Electronic signature API
Status	Early access
Apps included	3
From	$0.50 per envelope sent
Works with	Rutba Sign, Rutba Drive, Rutba CRM
Buy or trial	rutba.io/services/sign-api

The problem

Why it exists

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. The call does not touch your systems, so it keeps working whether or not your instance is up.

Fit

Who it is 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

Apps in this product

What you get

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 sits the formality desk that arranges a stamp, seal or notarisation your sender asked Rutba for.

SDK

A dependency-free client, one method per endpoint, held to the API’s own OpenAPI document by a test.

What it does

Capabilities

REST API with scoped, revocable bearer keys
Signed webhooks on every envelope event
A dependency-free client held to the OpenAPI document by a test
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, as proof they hold before the envelope seals
The agreement lifecycle through the same API: compose in one call, calendars, renewals, formalities with their stages

Commercial

Plans and pricing

Plan	Price	Includes
Free	Free verification, unlimited	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.50 per envelope sent	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	$99 per month, 500 envelopes	500 envelopes a month included, at well under the single-envelope rate; The same low rate 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	Committed volume pricing; Data residency options; A dedicated instance rather than the shared service; Named support and an SLA

Prices are in US dollars and exclude local taxes. Every plan is billed through rutba.io/services/sign-api. Annual and multi-product pricing is available on request.

Worth knowing Two backends, and the split is worth understanding before you build against it. The signing engine is a module inside your organization’s own instance, 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.

Rutba Suite

How it fits the rest of the suite

Rutba Suite is 23 products in three lines (the business suite, the workspace and the platform services underneath), sharing one customer list and one set of books. Buy the one you need today and add the rest later without a migration.

Rutba CRMRutba MarketingRutba CommerceRutba InventoryRutba OrdersRutba ManufacturingRutba FacilitiesRutba FleetRutba PeopleRutba BooksRutba MailRutba DriveRutba SignRutba Docs & SheetsRutba ChatRutba MeetRutba CallsRutba SendRutba MediaRutba SocialRutba Sign APIRutba StudioRutba Vision

Contact

Talk to us

Tech Style Ltd is a UK technology company building enterprise software, procurement intelligence and AI platforms. Tell us what you are trying to do and we will tell you honestly whether we are the right people for it.

This document online	www.tech-style.co/rutba/sign-api
Website	www.tech-style.co
Enquiries	hello@tech-style.co
Products	www.tech-style.co/products
Partner programme	www.tech-style.co/partners

This document was generated on request. It is built from the live content of tech-style.co at the moment you downloaded it, so it can never quote a price, a version or a status the site has since moved on from. Request a fresh copy any time at www.tech-style.co/downloads.

Take this away as a PDF

Rutba Sign API: Product Datasheet, typeset when you click, from the content above.

Download PDF All documents