A free e-signature API, without the metered sandbox.

Most hosted e-signature APIs want a credit card before you can send one real document. SigFetch's API is free, the same way the rest of it is free. Generate a key in your settings and start sending.

Read the API reference Get an API key

The reference is public — you don't need an account to read it.

The whole send loop

Five calls, start to finish. No SDK to install.

curl -X POST https://sigfetch.com/api/v1/envelopes \
  -H "Authorization: Bearer sf_..." \
  -d '{ "name": "Consulting agreement" }'

curl -X POST .../api/v1/envelopes/$ID/documents \
  -F file=@agreement.pdf

curl -X PUT .../api/v1/envelopes/$ID/recipients \
  -d '{ "recipients": [ { "name": "Ada Chen",
        "email": "ada@example.com",
        "role": "SIGNER" } ] }'

curl -X PUT .../api/v1/envelopes/$ID/fields \
  -d '{ "fields": [ { "type": "SIGNATURE", "page": 1,
        "x": 0.62, "y": 0.78, "width": 0.25, "height": 0.06 } ] }'

curl -X POST .../api/v1/envelopes/$ID/send

What you can call

POST/api/v1/envelopes: Create an envelope
POST/api/v1/envelopes/{id}/documents: Upload a PDF
PUT/api/v1/envelopes/{id}/recipients: Set recipients and roles
PUT/api/v1/envelopes/{id}/fields: Place fields for each recipient
POST/api/v1/envelopes/{id}/send: Send it
GET/api/v1/envelopes/{id}: Check status and signers
POST/api/v1/envelopes/{id}/void: Void an envelope in flight

What it tells you

Point a webhook at your own endpoint and SigFetch posts the events below, signed with an HMAC so you can tell the payload really came from here.

envelope.sent
recipient.signed
envelope.completed
envelope.declined
envelope.voided
envelope.expired

Delivery is best-effort and isn't retried, so treat a webhook as a nudge rather than a ledger. If your endpoint was down, ask for the envelope and read its current status.

The fine print

A key carries the same rights you have in the dashboard. There's no production tier to apply for and nothing metering your envelopes. Accounts are single-user for now, so the key is yours and not your team's.

If you're about to build something that will hammer this thing, email support@sigfetch.com first. I'd rather hear about it in advance than find out from a graph.

Everything the API sends is subject to the same evidence rules as the dashboard: consent is recorded, the finished PDF is hashed, and the verifier works on API-sent documents exactly like any other.

Ship it this afternoon.

Get an API key Read the API reference