Collect legally binding signatures on any PDF via REST — upload the document, place fields, send signing links, and receive a PKCS#7-sealed, tamper-evident file when all parties complete. No UI to build, no infrastructure to maintain.
Start free →POST your document as a multipart file upload. The API accepts any standard PDF — no conversion, no template setup required for one-off documents.
Specify field coordinates (page, x, y, w, h) and assign them to specific signers. Use the drag-drop field placer UI or pass coordinates directly in the API request.
Calling /send generates a tokenized, single-use signing link per signer and emails it. Signers verify identity with OTP and sign on a hosted page — no account required.
On completion, fields are flattened into the PDF, a PKCS#7 digital signature is applied, and an audit certificate is appended. Your webhook fires with the sealed document ready to download.
A document signing API is a web service that lets your application collect legally binding electronic signatures on documents without building the signing infrastructure yourself. You upload a document, specify who needs to sign and where their fields are, call a send endpoint — and the service handles signer notification, identity verification, signature capture, and returns a tamper-evident sealed document when all parties complete. GetSigned's document signing API is REST-based, works with any PDF, and returns a PKCS#7-sealed document with a hash-chained audit trail.
Any standard PDF — NDAs, employment contracts, service agreements, lease agreements, loan documents, consent forms, government applications, or any custom document you generate. GetSigned accepts PDFs up to 25MB and 500 pages with no pre-processing or conversion required. For recurring document types (like an NDA you send hundreds of times), you can define a template once and instantiate it per request without re-uploading the PDF.
Two ways: (1) Pass field coordinates (page, x, y, width, height) directly in the API request — useful when you generate documents programmatically and know the exact positions. (2) Use the drag-drop field placer UI — upload the document, drag signature fields to the correct positions visually, and save the layout as a template. The field placer is particularly useful for one-off external documents where you don't know the coordinates in advance.
Yes. Document signing APIs like GetSigned are built for legal defensibility under Canada's PIPEDA and the US ESIGN Act / UETA. Every signer verifies identity with an OTP, provides explicit e-sign consent that is logged with IP and timestamp, and the completed document is sealed with a CA-issued PKCS#7 digital signature. Any byte-level modification after sealing invalidates the signature — detectable by any PDF reader. A hash-chained audit log provides the evidentiary record.
GetSigned fires a webhook for every lifecycle event: envelope.declined when a signer declines, envelope.expired when the signing deadline passes without completion, and envelope.voided when the sender cancels. Your application receives these events and can take appropriate action — notify the sender, create a new envelope, or log the outcome. The declined or expired envelope and its partial audit trail are retained.
Most integrations are live within 4–8 hours. The minimal integration — create envelope, send, handle completion webhook, download sealed PDF — is three REST calls and a webhook endpoint. The full integration including error handling, retry logic, and status display typically takes one to two days. GetSigned's API is standard REST with multipart uploads for documents and JSON for everything else — no proprietary SDK to learn.
Related: Signable PDF API · Contract signing API · Integration guide · Legal validity
Free tier includes 25 envelopes per month. Full API access, PKCS#7 sealing, and webhooks from day one.
Get free API keys →