GetSignedBeta
Developers · Canada

E-signature API for Canadian software teams

Create envelopes, place fields, route signers, and receive webhooks over a clean REST API — with tamper-evident PKCS#7 sealing, a hash-chained audit trail, and data kept in Canada.

Read the docs →

Three calls from PDF to sealed document

1

Create an envelope

POST a PDF, your signers, and field coordinates to /v1/envelopes. A SHA-256 hash of the original document is captured on ingest.

2

Send for signature

POST /v1/envelopes/{id}/send generates tokenized signing links and dispatches notifications. Signers sign in any browser.

3

Receive a webhook

When all signers finish, an envelope.completed webhook fires. The sealed PDF is available at GET /v1/envelopes/{id}/document.

Create and send an envelope
curl -X POST https://api.getsigned.ca/v1/envelopes \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "document_url": "https://example.com/contract.pdf",
    "signers": [{ "name": "Avery Lee", "email": "avery@example.ca" }],
    "fields": [{ "type": "signature", "signer": 0, "page": 1, "x": 120, "y": 640, "w": 180, "h": 48 }]
  }'

# Then dispatch signing links:
curl -X POST https://api.getsigned.ca/v1/envelopes/$ENV_ID/send \
  -H "Authorization: Bearer $TOKEN"

Frequently asked questions

Is there an e-signature API hosted in Canada?

Yes. GetSigned exposes a REST API and stores signed documents and signer data in Canada. That keeps Canadian organizations’ privacy and procurement reviews simpler than routing documents through a US-only provider. See the data residency page for specifics.

How do I authenticate to the API?

Integration access uses OAuth2 client-credentials. Each application gets a client ID and secret, which you exchange for a short-lived bearer token. There are no long-lived API-key strings embedded in requests.

What document formats are supported?

Upload standard PDFs. Word documents can be converted to PDF before signing on supported plans. Fields (signature, initial, date, text, checkbox) are positioned with page coordinates.

Does the API seal documents automatically?

Yes. You do not call a separate sealing endpoint. On completion, GetSigned flattens fields, appends an audit certificate page, and applies a service-level PKCS#7 digital signature before the completion webhook fires.

Can I embed signing inside my own app?

Yes. You can redirect signers to a tokenized link or embed the signing experience in your product. See the embedded signing guide and the SaaS integration guide.

What happens to documents over time?

Documents follow a retention policy: the sealed blob is purged after the retention window, while the documents record and the hash-chained audit log are kept so the executed record stays verifiable. Retention is configurable per tenant.

Related: API docs · Quickstart · Digital signature API · E-signatures for SaaS · Security · Data residency

Build Canadian signing into your app

Free API keys to start. OAuth2, webhooks, and tamper-evident sealing on every envelope.

Get free API keys →