A familiar experience.
Configure document branding and an allowed embedding origin for an integrated signing experience.
THE SIGNATURE IS PART OF YOUR PRODUCT
Your workflow.
SignedOff behind it.
Bring document preparation and signing into the software your customers already use.
From a PDF to
a completed record.
Upload a document, assign its fields and people, create signing links, and retrieve the completed record.
Your application controls its invitations and integration experience. Keep API credentials on your server and confirm completion from the server before updating your own records.
Get API Developer ↗A typical integration WORKFLOW OVERVIEW
- 01 Upload your PDF
- 02 Configure people & fields
- 03 Create signing links
- 04 Follow document status
- 05 Retrieve PDF & evidence
Built to fit into your product’s flow.
A record you can use.
Retrieve the original and completed PDFs with portable signing evidence and document hashes.
Usage that stays clear.
API Developer is $99 per month, including 250 documents. Additional documents are $0.50 each.
API billing is separate from workspace billing. Review the integration guide for current endpoints and requirements.
Open live API guide ↗Create a document from your server.
Keep your API key on your server. Send the PDF as the request body with a bearer token and a stable idempotency key. Identical retries with the same key do not create an additional billable document.
curl --request POST \
"https://app.signedoffdocs.com/api/v1/documents?title=Service%20agreement&external_id=record-123" \
--header "Authorization: Bearer $SIGNEDOFF_API_KEY" \
--header "Content-Type: application/pdf" \
--header "Idempotency-Key: record-123-agreement-v1" \
--data-binary @agreement.pdfThe response includes the document ID, revision, page count, and original hash. Next, configure the recipients and fields using the API guide. Your application sends invitations.
Embedding, events, and limits
Hosted embedding requires an exact allowed origin in branding.embedOrigin. Signers verify their email with a code. Webhooks use HMAC-SHA256 signatures and retry delivery up to eight times; verify signatures before processing events.
PDFs must be flat, unrotated, and uncropped, with a maximum of 4 MiB and 50 pages. The API supports up to 500 signers and 1,000 fields per document, and 10 webhook endpoints per account.
API Developer is billed separately from Free, Solo, and Business workspaces: $99/month includes 250 document creations, then $0.50 per additional document.
YOUR NEXT AGREEMENT STARTS HERE
A little less paperwork.
A little more possibility.
Get started free ↗3 documents a month. No subscription required.