Skip to content

OV document-signing certificates are available on Signyd. Sign with your organization's name. Request a quote

Signyd API

Signatures, built into your product.

Create a document, add recipients and send signing invites with one REST call. Follow every signature with HMAC-signed webhooks.

Base URL

https://app.signyd.com/api/v1

Authorization: Bearer sk_live_…

GET /documents

POST /documents

POST /documents/:id/send

GET PATCH /webhooks

From zero to a sent document in three steps

  1. 1

    Create a key

    In the app, open Settings → API (owners and admins) and create a named live key. Copy it right away: Signyd shows the secret only once.

  2. 2

    Send a document

    POST a PDF (base64) with its recipients to /documents. Signyd sends the signing invites for you.

  3. 3

    Listen for events

    Set your HTTPS webhook URL and receive an event when a document changes status or a recipient signs.

Use cases

What teams build with it

Each flow below uses only the endpoints you see in the reference.

  • Contracts at checkout or sign-up

    When a customer accepts a plan, generate the agreement from your own data and send it for signature without anyone leaving your flow.

    POST /documents
  • Onboarding with verified identity

    Mark a recipient with kyc_required to require Signyd Verify before they sign: ID, proof of life and face match.

    POST /documentskyc_required: true
  • Keep your CRM or ERP in sync

    Receive a webhook when a request is sent, completed, voided or expired, and update the deal, order or case on your side.

    WebhooksGET /documents/:id
  • A signing dashboard

    List your latest documents and their status (draft, sent, partially signed, completed, voided, expired) inside your own back office.

    GET /documents
  • Nudge pending signers

    Resend the invitations for documents that are still waiting, from a button in your app or a scheduled job.

    POST /documents/:id/send
  • Archive with proof

    Store each document's SHA-256 hash alongside your records to show later that the file has not changed.

    GET /documents/:idsha256_hash

Code samples

Your language, one request away

Pick a language and an operation. Samples read your key from SIGNYD_API_KEY.

# PDF as base64 (macOS: base64 -i agreement.pdf)
PDF_B64=$(base64 -w0 agreement.pdf)

curl -X POST https://app.signyd.com/api/v1/documents \
  -H "Authorization: Bearer $SIGNYD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Service agreement",
    "filename": "agreement.pdf",
    "pdf_base64": "'"$PDF_B64"'",
    "recipients": [{
      "email": "ada@example.com",
      "name": "Ada Lovelace",
      "kyc_required": false,
      "page_number": 1,
      "signature_x": 72,
      "signature_y": 72
    }]
  }'
# → 201 Created: the document and its recipients

Endpoints at a glance

MethodPathWhat it does
GET/documentsList up to 50 documents in your workspace.
GET/documents/:idGet one document, with its recipients.
POST/documentsCreate a PDF, add recipients and send the signing invites.
POST/documents/:id/sendResend the invitations for a document.
GET/webhooksRead your webhook URL and whether a secret is set.
PATCH/webhooksSet the webhook URL and optionally rotate the secret.

Document statuses

  • draft
  • sent
  • partially_signed
  • completed
  • voided
  • expired

Signed webhooks

Signyd sends a POST with JSON to your HTTPS endpoint for your organization's events. Answer with a 2xx quickly; failed deliveries are retried.

EventWhen
Document status updatesA request is sent, completed, voided or expired.
Recipient signedA signer finishes.
kyc.failedIdentity verification failed or the requester declined (reason may be requester_denied).

Verify every delivery

  1. 1Read the raw request body, before any JSON parsing.
  2. 2Compute the HMAC of that body with your webhook secret.
  3. 3Compare it with the signature header, and reject the request if it does not match.
Webhooks documentation

Limits and errors

Recipients per document
Starter 10 · Pro and Business 40 · Scale 99
PDF size
Up to 15 MiB
Documents per list call
Up to 50
Signature position
Defaults to 72, 72 on page 1
Credits
A multi-party request uses a monthly envelope when the signing process completes

Error responses

Statuserror
401unauthorized
400invalid_json · too_many_recipients · invalid_pdf · pdf_open_encryption · validation messages
402no_credits · no_kyc_credits
404not_found
413payload_too_large

Build the signing flow your product needs

Create a free account, generate a key and send your first document today.