Changelog

Documents

• New endpoint GET /docs/{documentId}/recipient-links — fetch one unique signing link per recipient so you can distribute signing links yourself over any channel instead of relying on Formify's email/SMS/WhatsApp invitation.
• New per-signee flag disableInvitationMessage in signeeDetails (on POST /docs and the draft flow) — suppresses Formify's own invitation for that recipient. The signing link is still created and signable.
• Security: self-distributed links are verification-locked — opening one requires a one-time code that Formify sends to the recipient's contact method on file, so a leaked link cannot be opened by anyone else. The lock is enforced regardless of the document's other verification settings.
• A recipient with both an email and a phone is returned as two links (one per verificationChannel); a recipient with no contact method on file is omitted from the response.

Authentication

• Added POST /auth/token to exchange a Formify API key for a short-lived Bearer access token.
• Updated the MCP Server guide with API key fallback instructions for clients that cannot complete OAuth/PKCE and only accept a pasted token.
• OAuth with PKCE remains the recommended connection method where supported.

Guides

• New guide: PDF Form Attributes, covering tink-* field attributes for validation, verification, ID scanning, attachments, and auto-populated values.

Drafts

• New endpoints for managing draft documents — save document configuration without sending invitations to signees.
• POST /docs/drafts — create a new draft.
• PUT /docs/drafts/{draftId} — update an existing draft.
• GET /docs/drafts — list drafts with pagination.
• GET /docs/drafts/{draftId} — get full draft details.
• GET /docs/drafts/{draftId}/file — get a preview PDF of the draft with signature fields placed.
• GET /docs/drafts/{draftId}/file-url — get a short-lived, one-time download URL for the draft PDF (no auth header required to follow the URL).
• GET /docs/drafts/{draftId}/file-download/{token} — anonymous endpoint that streams the draft PDF using a one-time token from /file-url.
• POST /docs/drafts/{draftId}/send — convert a draft into a live document and send invitations.
• DELETE /docs/drafts/{draftId} — permanently delete a draft.
• Signee details, contact methods, and signature coordinates are all optional during the draft phase — full validation occurs only when the draft is sent.

OAuth for AI & Third-Party Clients

• Added support for OAuth Client ID Metadata Documents, allowing public clients (such as MCP servers and AI connectors) to authenticate using an HTTPS URL as their client_id — no pre-registration or client_secret needed.
• New endpoint POST /oauth/register for Dynamic Client Registration. Programmatic OAuth client registration for platforms that cannot host a metadata document.
• All public clients use PKCE (S256) for security. New code_verifier parameter on POST /oauth/token.
• Updated POST /oauth/revoke to support token revocation for public clients.
• Updated OAuth Authorization Server Metadata with registration_endpoint.
• New guide: MCP Server.
• New guide: OAuth for AI & Third-Party Clients (covers both metadata documents and DCR).

Account Capabilities

• New endpoint GET /account/capabilities for discovering which features and add-ons are enabled for the account.
• Use this endpoint before using optional features to avoid unexpected 403 Forbidden responses.

AI Assistant

• Possibility to enable AI assistant for new documents. Requires the aiAssistant capability.

Signature Methods

• Additional signature methods available for new documents: bankid_identification, digital_ink_id_scan, and face_liveness. Check GET /account/capabilities for which methods are enabled on the account.

Webhook Signature Verification

• Support for securing webhooks with HMAC-SHA256 signature verification.
• New signingSecret returned on webhook creation and retrieval.
• New endpoint POST /webhooks/{webhookId}/rotate-secret to rotate signing secrets.

OAuth

• Fixed parameter name from scopes to scope to follow OAuth 2.0 standard (RFC 6749). The old name scopes is still accepted as a fallback.

Signing Order

• Possibility to provide a signing order for signature requests in documents.

Personal Message

• Possibility to provide a personal message for document signature request invitations (email, SMS, or WhatsApp).

Phone Delivery Methods

• Option to use WhatsApp as text message delivery method when a phone number is used.

Templates

• Added support for templates, allowing documents to be created based on pre-configured templates via POST /docs using the new templateId parameter.
• Introduced endpoints for listing and getting template details (GET /templates, GET /templates/{templateId}). Note: creating templates is still only possible through the Formify web app.

Fields and Field Values

• Updated POST /docs to support pre-filling form fields using the fields property.
• Added endpoints for getting fields (GET /docs/{documentId}/fields, GET /files/{fileId}/fields, GET /templates/{templateId}/fields).
• Added endpoint for setting editable field values in open documents (POST /docs/{documentId}/field-values).
• Added endpoint for getting field values for completed documents (GET /docs/{documentId}/field-values).

Fields Read-Only Mode

• Added fieldsReadonlyMode setting for controlling read-only mode for form fields within documents.

Signature Fields

• Possibility to edit contact details for signature fields not yet signed in documents sent for signing.

• Initial release.