sign.ytDocs

Build on sign.yt

Send PDFs for signature, track every step with signed webhooks, and download sealed, verifiable documents. One REST API for every organization on the platform.

Your first API call#

All requests go to https://api.sign.yt/v1 and authenticate with an API key in the Authorization header. Create a key in the app under API keys (organization admins only, on plans that include API access), then list your documents:

export SIGNYT_API_KEY="sk_live_..."

curl -sS "https://api.sign.yt/v1/documents?limit=5" \
  -H "Authorization: Bearer $SIGNYT_API_KEY"

The response is a JSON array of document summaries:

[
  {
    "id": "3f1c2a9e-5b7d-4c11-9a3e-0d4b8e2f6a71",
    "title": "Office lease",
    "status": "PENDING",
    "recipients_count": 2,
    "created_at": "2026-10-19T08:30:12.418204Z",
    "sent_at": "2026-10-19T08:31:02.110931Z",
    "completed_at": null,
    "folder_id": null,
    "team_id": null
  }
]

Install an SDK#

pip install signyt

No SDK for your language? The API is plain HTTPS + JSON (multipart for PDF uploads), so any HTTP client works. See PHP and other languages.

What you can build#

  • Documents: upload a PDF, add recipients and fields, send, remind, cancel, download the signed PDF and the audit trail. Documents and recipients
  • Templates: reusable PDFs with field layouts, plus public signing links and QR codes. Templates and public links
  • Bulk sending: one PDF, one CSV, up to 500 drafts per call. Bulk sending
  • Flows: multi-step automation with approvals, waits and notifications. Flows
  • Webhooks: HMAC-signed events for every state change. Webhooks
  • Evidence: PAdES-sealed PDFs, hash-chained audit log, optional post-quantum seal and Bitcoin anchoring. Verification and evidence

Reference#