Reference
Changelog
Notable changes to the public API, webhooks, SDKs and evidence features. Changes within /api/v1 are additive; see versioning.
2026-10: Dedicated API host#
- The API is now served on
https://api.sign.yt/v1. It accepts API keys only (browser session cookies are ignored).https://sign.yt/api/v1keeps working; the Python and TypeScript SDKs default to the new host from 0.2.1. Conventions
2026-10: API key IP allowlist#
- API keys can be restricted to IPv4/IPv6 addresses and CIDR ranges. Other callers get
403 ip_not_allowed; empty list = any address. Restrict a key to IP addresses
2026-10: Error detail is always a string#
- Breaking for clients that read
detail.code:detailis now always the same string asmessage(the422field-error list is unchanged). Branch on the top-levelcodeand showmessage, which every error has always carried; error-specific data that used to sit insidedetailis inextra. Errors GET /documents/{id}/intakereturns204when the document has no recipient start form (was404 intake_not_found).
2026-10: Identity verification#
- Didit identity provider (ID document + selfie with liveness, worldwide) alongside Authologic and login.gov.pl, with a manual-review status
IN_REVIEW. Identity verification GET /documents/{id}returnsverification_typeand each recipient's latest check asrecipients[].identity_verification(status and provider only).- New webhook
recipient.identity_verification_updated. Webhook events - Senders are emailed when a signer's check is declined or abandoned; the review-result email to the signer now includes their signing link.
2026-10: Agents, redirects, embedding#
- Remote MCP endpoint
/api/v1/mcp(Streamable HTTP, API-key auth, scope-filtered tools) and a newplace_signature_fieldstool. MCP server redirect_url_after_signon document create, template use, bulk send and campaigns, plusPATCH /documents/{id}; optional org allowlist of redirect domains. Redirect after signing- Embedded signing (Business+):
/embed/sign/<token>framable by the org's allowed origins, withpostMessageevents. Embedding
2026-10: API polish#
- Unified error envelope on every error:
code,message,detail(legacy),request_idand optionalextra. Errors - Cursor pagination for
GET /documentsandGET /webhooks/{id}/deliveriesviacursor,X-Next-CursorandLink: rel="next";offsetkeeps working. Pagination - Rate-limit headers
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reseton API-key responses. Rate limits - New webhook emissions:
document.viewed(first open of a signing link) anddocument.signed(each signature). Payload schemas documented for every event. Webhook events - New developer docs at docs.sign.yt with a self-hosted API reference.
2026-10: Evidence and verification#
- Public verification links on
verify.sign.yt/<code>, printed as a QR code on the certificate of completion. - OpenTimestamps (Bitcoin) anchoring of completed documents and a downloadable evidence bundle (
GET /documents/{id}/evidence.zip). - Post-quantum evidence seal v2 (ML-DSA-65 + Ed25519), downloadable with
GET /documents/{id}/pq-seal. - PAdES time-stamping with a fallback list of timestamp authorities; B-LTA platform seal when a TSA is available.
- Explicit signing consent recorded with every signature; hardened audit and signature hash chains.
2026-10: Documents#
POST /documents/{id}/canceltakes areason, notifies everyone involved and can create a corrected draft (copy_as_draft); emitsdocument.cancelled.PATCH /documents/{id}/recipients/{recipient_id}corrects a recipient's email, name or phone.GET /documents/{id}/recipients/{recipient_id}/signing-linkreturns a pending recipient's signing link (audited).- Plan feature gating for API keys and webhooks (
402 feature_not_in_plan).
2026-04: Foundations#
- Webhook deliveries with HMAC-SHA256 signatures over timestamp and body, retries with backoff and a dead-letter state; SSRF protection for webhook URLs.
Idempotency-Keysupport on unsafe methods and capped pagination on list endpoints.- PAdES platform seal with RFC 3161 timestamps.