For developers and AI agents
Signing inside your product.
Send from your own system, let customers sign without leaving your app, and hear about every signature. The specification is public, and sandbox keys come with every plan, Free included.
Build on sandbox keys first. Pay when you go live.
# 1. Build it. Nobody is emailed yet. POST /api/v1/envelopes Idempotency-Key: 0c6f…e41a { "template_id": "…", "values": { … }, "send": false } # 2. Send it when a person says so. POST /api/v1/envelopes/{envelopeId}/send # 3. Later, to your endpoint. Check the signature first. Vumasign-Signature: t=…, v1=… { "type": "envelope.sealed", "sandbox": false, … }
Your code sends answers, not coordinates.
No boxes placed by pixel. You fill in named fields, and the template knows where they go.
Describe the form once.
Upload the PDF to a template and every field is found and named. Each envelope made from it asks for the same things in the same places.
Some people never sign.
Dependant 1 is a subject, not a recipient. One application can collect six people’s details and be signed by two.
Building is not sending.
Create, check, then send: two calls, on purpose. A bug in your loop costs you a draft, not four hundred emails to real customers.
Embedded signing
Your customer never leaves your app.
Mint a signing link for one recipient and open it in your own page. It tells you when it's on screen, when the signer finishes and when they decline. The webhook tells you when the sealed document is ready.
Embedded signing guide// Signing runs inside your page. Listen for what happens. window.addEventListener('message', (event) => { switch (event.data.action) { case 'ready': hideSpinner(); break // Finish was pressed. Not completion: wait for the webhook. case 'signed': showNextStep(); break case 'declined': askWhy(); break } })
AI agents
An agent prepares it. A person sends it.
Two MCP servers. The docs server lets an agent writing your integration search the real reference instead of inventing endpoints. It holds no key.
The account server runs on your machine with your own key. It reads templates, checks values and prepares drafts. It never sends, and never mints a signing link.
The draft is ready with the deal details filled in and checked against the template. Review it and send.
Built for code that retries.
Networks drop. Templates change. People hand things on. None of it should send twice or fill the wrong box.
Every field has a name.
Each field carries a data_key and the person it is about, like person.sa_id_number on the subject spouse. Check values against the template before you send, and pass its etag so a template renamed since is refused rather than filled wrongly.
Retry without fear.
Creating an envelope, a batch or a template requires an Idempotency-Key. Send a timed-out request again with the same key and it cannot make a second envelope or email anyone twice.
Webhooks you can trust.
HMAC-SHA256 over the timestamp and the raw body, so a replayed or altered delivery is refused. Every event has an id to deduplicate on and a sandbox flag that tells a rehearsal from the real thing. On every plan.
Hand over, or send in bulk.
A signer can pass the document to a colleague, who takes their place, and your endpoint is told. Send a batch from one template in one call, with an idempotency key like any other create.
Docs generated from the code that serves them.
The reference, error codes, scopes and webhook events at docs.vumasign.com come from the product's own OpenAPI document, not a hand-kept copy. Try any call in the playground, or copy it in curl, Python, JavaScript or Go.
Pricing
One rate, at any volume.
No tiers to buy and no bands to reach. Every envelope past the first 50 costs the same, so the bill is volume times rate.
R500 a month is a minimum, not a cap. An API account is never refused for going over it.
Prices in rands, billed monthly. Vumasign (Pty) Ltd is not registered for VAT, so no VAT is charged on these prices.
Platform plans are priced separately and cannot mint live keys.Platform pricing
Live keys, embedded signing and the integration surface. 50 envelopes included, then the published rate.
- Live API keys — the only plan that can mint them
- Embedded signing URLs, minted per recipient
- Signed webhooks, as on every plan
- Your own sending domain and brand
- 100 mobile codes a month, then R0.50 each
- Identity checks at R59 a signer
- Everything the platform plans do, except single sign-on
| First 50 each month | Included |
|---|---|
| From 51 | R10 |
Build it before you pay for it.
Sandbox keys are on every plan, Free included. Read the docs, build the integration, and switch to live keys when it works.
Signed, sealed, sorted. Lekker.