For developers
Send for signature from your own code.
One call sends a PDF. People sign on your site, in an iframe. Your server gets the signed copy.
Plain REST and JSON
Signing inside your app
Signed webhooks
The same sealed record as the app
Get an API key Free plan included. No card to start.
Send
A PDF in, signers out.
Keys are made on Sign a PDF → Integrations. Every call carries one.
1 Send the envelope
Post the PDF with a data part: who signs, in what order, and where each field sits as a fraction of the page from its top-left corner. Or give a template_id and only the names.
It goes out at once. Add "send": false to keep a draft.
# the PDF + one JSON part
curl https://superoffice.online/api/v1/envelopes \
-H "Authorization: Bearer $SO_KEY" \
-F file=@lease.pdf \
-F 'data={
"title": "Lease 14B",
"recipients": [
{ "name": "Asha Rao", "email": "asha@example.com" }
],
"fields": [
{ "recipient": 0, "type": "signature",
"page": 1, "x": 0.12, "y": 0.78 }
]
}'
# 201 → { "envelope": { "id": "b7Qk…", "status": "sent",
# "recipients": [{ "id": "r1", "status": "sent", … }] } }
2 See where it stands
Each signer's status: sent, viewed, signed or declined. Remind the ones whose turn it is, or void it with a reason the signers see.
curl https://superoffice.online/api/v1/envelopes/$ID \
-H "Authorization: Bearer $SO_KEY"
curl -X POST https://superoffice.online/api/v1/envelopes/$ID/remind \
-H "Authorization: Bearer $SO_KEY"
curl -X POST https://superoffice.online/api/v1/envelopes/$ID/void \
-H "Authorization: Bearer $SO_KEY" \
-H "Content-Type: application/json" \
-d '{ "reason": "Wrong unit number" }'
3 Get the signed copy
Once everyone has signed: the sealed PDF and its certificate of completion. Or let the envelope.completed webhook bring you both links.
curl https://superoffice.online/api/v1/envelopes/$ID/files/final \
-H "Authorization: Bearer $SO_KEY" -o signed.pdf
curl https://superoffice.online/api/v1/envelopes/$ID/files/certificate \
-H "Authorization: Bearer $SO_KEY" -o certificate.pdf
Embedded signing
They sign without leaving your app.
List your site on Integrations once. Then ask for a signing URL each time someone is ready.
1 Ask for a signing URL
Mark the signer "embedded": true when you send, and we never e-mail them. The URL works once and for 5 minutes, so ask for it when the page loads.
curl -X POST \
https://superoffice.online/api/v1/envelopes/$ID/recipients/$RID/embed \
-H "Authorization: Bearer $SO_KEY" \
-H "Content-Type: application/json" \
-d '{ "origin": "https://app.example.com" }'
# → { "url": "https://superoffice.online/esign/em_…",
# "expires_at": "…", "single_use": true }
2 Put it in an iframe and listen
Only the sites you listed can frame the page. When the person signs or declines, the page tells yours.
<iframe src="EMBED_URL" style="width:100%;height:90vh;border:0"
allow="camera"></iframe>
<script>
window.addEventListener('message', (e) => {
if (e.origin !== 'https://superoffice.online') return;
if (e.data.type === 'superoffice:signed') showThanks();
if (e.data.type === 'superoffice:declined') showDeclined();
if (e.data.type === 'superoffice:error') askForANewUrl();
});
</script>
Limits
What one key may do.
A busy integration stays well inside these. A 429 says when to try again.
Limits of the SuperOffice API
Limit Value
Requests per key 120 a minute
New envelopes per key 20 a minute
Signing URLs per key 60 a minute, each valid 5 minutes, once
PDF Up to 50 MB and 300 pages
Recipients Up to 20 per envelope, in steps or all at once
Free plan The same caps as the app: 10 envelopes sent, one envelope's signed copy free to download
Events to your server: see Integrations for webhooks and Zapier.
Start
Your first signed PDF, from curl.
Make a key, send yourself a test envelope, sign it on your phone. Questions go to work@superoffice.online.
Get an API key
No account yet? Start free , no card.
✓ Signed by everyone