For developers

Sign, seal and verify from your own software Beta

One call seals a PDF. One more sends it for signing. Anyone can check the result at verify.onwyn.io. Built for ERP and business-software vendors who want signing inside their own product.

Request an API key See the calls Check a document

During the Beta, Onwyn issues each API key by hand. Tell us your company's exact legal name: it is printed on every seal.

Your first seal in three steps

  1. Get a key

    Keep it on your server, in an environment variable. Never put it in a browser or an app.

    export ONWYN_API_KEY='onwyn_test_XXXXXXXX'
  2. Seal a PDF

    The sealed PDF comes back in the same call. The header X-Onwyn-Code carries its code.

    curl -sS --max-time 120 -D - -o sealed.pdf \
      -H "Authorization: Bearer $ONWYN_API_KEY" \
      -F file=@invoice.pdf -F ref=INV-2026-0001 \
      https://sign.onwyn.io/api/seal
  3. Check it

    The check is public and needs no key. Change one character in the file and upload it again: the check says it was changed.

    curl -sS https://verify.onwyn.io/api/v1/verify/code/ONW-4K7P-2M9X-QB3T

Seven calls

Five calls on the sign host, each with your API key. Two on the verify host, public and free.

CallWhat it does
POST /api/sealSend a PDF. Get the sealed PDF back in the same call.
POST /api/signSend a PDF and up to 10 signers. Get a signing link for each signer.
GET /api/sign/{id}See how far the signing has got, signer by signer.
GET /api/sign/{id}/documentDownload the finished PDF.
GET /api/sign/{id}/progress-copySeveral signers: a copy after the first signature. Not sealed, not final.
GET /api/v1/verify/code/{code}Check a code. Public, no key.
POST /api/v1/verify/uploadCheck a PDF file. Public, no key.

Send a document for signing

The answer carries a signing link for each signer. You show the link in your product or send it yourself. The signer opens it in a browser, reads, consents and signs, with no account and no app. With a return address, the browser then comes back to your product.

curl -sS --max-time 120 \
  -H "Authorization: Bearer $ONWYN_API_KEY" \
  -F file=@quotation.pdf -F 'signer_name=Anna Muster' -F ref=SO42 \
  -F return_url=https://erp.example.com/orders/42 \
  https://sign.onwyn.io/api/sign
Several signers.
Up to 10, one after another or all at once.
Where the signature goes.
Write {{sign:1}} and {{date:1}} into the PDF, or send the page and the position.
Sign only.
Send seal=false to get the signatures without the Onwyn seal.
Your customer's name on the seal.
Selling to many companies? Send company_name with each call, and the seal names your customer as well as you.
Waiting for the result.
Ask for the status every 5 to 10 seconds, or when the signer comes back to your return address. Then download the document.
The same in Python
import os, requests

BASE = "https://sign.onwyn.io"
AUTH = {"Authorization": f"Bearer {os.environ['ONWYN_API_KEY']}"}

with open("quotation.pdf", "rb") as f:
    r = requests.post(f"{BASE}/api/sign", headers=AUTH, timeout=120,
                      files={"file": ("quotation.pdf", f, "application/pdf")},
                      data={"signer_name": "Anna Muster", "ref": "SO42"})
r.raise_for_status()
request = r.json()
print(request["signers"][0]["signing_url"])   # give this link to the signer

status = requests.get(request["status_url"], headers=AUTH, timeout=30).json()
if status["status"] == "completed":
    pdf = requests.get(status["document_url"], headers=AUTH, timeout=60).content

Good to know before you build

  • Through the API, Onwyn sends no email. You give each signer their link, and whoever opens it can sign. The evidence record says so.
  • A call that is sent again makes a new document. Use a timeout of 120 seconds. On 503 busy, wait for the seconds in Retry-After, then try again.
  • There are no webhooks on this API yet. Ask for the status instead.
  • A PDF can have up to 25 MB and 100 pages. Each address can make 30 seals and 30 signing requests a minute, and up to 500 documents a day.
  • During the Beta, Onwyn keeps its copy of a document for 30 days. Download what you need and keep it.
  • Every error is JSON with a short code and a plain sentence that says what to change.
  • It is a simple electronic signature, sealed with Onwyn's own certificate and clock. What the Beta is and is not.

Your key comes with the full API reference, with examples in curl, Python, PHP and Node, written so you can hand it to an AI coding assistant.

Send your developers to us

We plan the integration with your team: which calls to use, where the signature goes, and how your customers' names appear on the seal.

Plan an integration with us

The API costs the same as the web app. See pricing.