The API-first e-sign platform for SaaS teams: embed legally binding signatures with one POST, signed webhooks, real SDKs, and a free 500-contract sandbox.
Send documents, capture consent, receive HMAC-signed webhooks, and store the sealed audit trail — without leaving your product's flow.
curl https://api.ziasign.com/v1/contracts \
-H "Authorization: Bearer $ZIASIGN_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"subject": "Subscription Agreement — Acme",
"documents": [{ "name": "agreement.pdf", "data": "<base64>" }],
"signers": [{ "email": "[email protected]", "name": "Jane Doe" }],
"webhook_url": "https://app.example.com/webhooks/ziasign"
}'Every platform capability — send, route, remind, seal — is exposed through the same REST API our own apps use. No second-class endpoints.
HMAC-signed, retry-safe events for envelope sent, viewed, signed, completed. Idempotent by design so replays never corrupt state.
Server-to-server tokens, scoped API keys, OAuth2/JWT patterns, and per-tenant isolation for multi-tenant SaaS.
ESIGN, UETA, eIDAS alignment with RFC 3161 timestamps and SHA-256 hash-chained audit trails your customers can rely on.
Free sandbox, production tiers from published rates, pay for contracts shipped — forecastable COGS for your product.
Stable versions stay stable. Breaking changes carry a 24-month deprecation window, so your roadmap is yours.
A SaaS eSignature API lets your product create, send, and track legally binding e-signatures programmatically — your users sign inside your app while the API handles identity, consent capture, audit trails, and compliance.
With ZiaSign: create a contract via one POST to /v1/contracts with your document and signers, receive signing links or embed the flow, then listen for HMAC-signed webhooks for viewed/signed/completed events. Typical integrations ship in an afternoon.
Yes. The ZiaSign sandbox includes 500 production-shaped contracts, free, with the same API surface as production. No credit card and no sales call required.
Yes. Signatures created through the ZiaSign API are legally binding in 180+ countries under ESIGN, UETA, and eIDAS, with court-ready audit trails (RFC 3161 timestamps, SHA-256 hash chain).
API-first means the API is the product, not an add-on: full capability parity with the UI, real SDKs, signed webhooks, semantic versioning with long deprecation windows, and pricing designed for programmatic volume.
500 sandbox contracts, same API shape as production, published pricing when you ship.