eDocInk

Signatures inside your app

eDocInk is a signing API for applications. Your app sends the document and delivers the link. People sign on pages that carry your customer's brand. You get evidence you can verify yourself.

Request sandbox accessConnect with an AI agent

At a glance

Cost The sandbox is free. Production is free for pilot customers; pricing will be published before general availability.
Getting a key Request sandbox access at /access and confirm by email. Guest-signing credentials usually arrive within a few minutes. Agents can ask for their developer through POST /api/access.
Smallest integration Four calls to send a document, one to check it, one to verify it. See the quick start.
What you get that others don't Evidence your app can verify on its own, with keys it pins, that anyone else can check against our published keys (which means trusting us for the key list), plus an independent timestamp that needs no trust in us.

How it works

  1. Prepare. Your server sends the document text. eDocInk returns the exact text that will be signed and its SHA-256.
  2. Create and invite. Your server creates a signing request and gets a single-use signing link for each signer.
  3. Deliver. Your app sends the link, by email or in-app, under your own name. eDocInk sends no email.
  4. Sign. The signer reviews the document on a hosted page (which can carry the business's name, logo and colour if you send them to us), agrees to the consent text and signs.
  5. Verify. Your app learns the outcome by webhook or event feed, fetches the evidence and verifies it against public keys it has pinned.

What eDocInk does, and what your app does

eDocInk Your application
Freezes the exact document text and its SHA-256 Decides what the document says and who may send it
Hosts review, consent and signature pages Decides who signs, and delivers each signing link
Shows the business's branding on the signing pages, once the operator has set it Sends the email or in-app message
Records consent and how the link was used Updates its own records when something is signed
Signs evidence for every signature (Ed25519) Verifies the evidence and keeps it
Isolates every app and business from every other Keeps its API key on its server only

Good to know

  • Server to server. Every call is HTTPS with a bearer key and a tenant id. Keys never go to a browser or phone.
  • Safe retries. Every POST takes an idempotency key, so a timeout never creates a duplicate.
  • Several signers. Envelopes collect every required signature on one document.
  • Documents: plain text up to 200,000 bytes (about 30,000 words), PDFs up to 10 MiB, or operator-published templates. Word, OpenDocument, RTF, HTML, text and image files convert to PDF first.
  • Independent timestamps. An outside timestamp authority (DigiCert) timestamps the evidence for every signature. That fixes when the evidence existed, from a source independent of your app and of us. Live in the sandbox and production.
  • Staying current. Your app reads what changed from the API itself (notices and a compatibility check), and the changelog lists every release.
  • Not yet: identity proofing of guest signers. A guest email link proves control of the link, nothing more.

Get started

  • Get access: request sandbox credentials.
  • Guides: integration requirements, API reference, OpenAPI file, changelog.
  • For AI agents: a step-by-step guide an agent can follow to connect an app.
  • Demo: a working app built on eDocInk (passcode required).
  • Feedback: tell us what was unclear, broken or missing.

Guides

Agent guide

Step-by-step instructions for an AI coding agent to connect an application to eDocInk.

Integration requirements

What an application needs and must do: calls in order, idempotency, storage, delivery, webhooks, evidence, errors, go-live checklist.

API reference

Every v1 operation, header, scope, status and schema, generated from the OpenAPI contract.

Changelog

What changed in each release, which SDK supports it and what your app needs to do. Also as an Atom feed.