1.6.0 2026-11-11

Public links

  • New: HTML form prefill through the API. GET /links/{linkId}/prefill returns the fields that can be prefilled, the websites allowed to prefill the link, and per website the form code and developer instructions. POST /links/{linkId}/prefill/websites allows a website for chosen fields or replaces its fields, and DELETE /links/{linkId}/prefill/websites?website=… stops it. These are the same settings as in the Formify app. See HTML Form Prefill.
  • GET /account/capabilities has a new flag, htmlFormPrefill.

MCP

  • New tools get_link_prefill, set_link_prefill_website and remove_link_prefill_website, so an assistant that has created a public link can also set up prefill from your website. It confirms the website and the fields with you first.
1.5.4 2026-11-11

Guides

  • New guide: HTML Form Prefill. A form on your own website can send visitors into a public link with fields already filled in, using a plain HTML form POST and no API key. The link's owner allows each website and chooses which fields it may prefill; Formify generates the form code and developer instructions for the link.

API

  • No changes to the REST API.
1.5.3 2026-11-11

Signature placement

  • signatureBox and idScanBox now accept decimal values for x and y (PDF points, origin top-left), for example 120.5. Whole numbers keep working as before.
  • A coordinate that is not a valid number now returns 400 Bad Request naming the property, instead of being silently reset to 0.

Documentation corrections

  • PATCH /docs/{documentId}/signature-field: reaching the update limit (cooldown) returns 400 with a plain-string message, not 429. The documentation previously said 429.
  • POST /docs/{documentId}/reminder: reaching the reminder limit returns 200 with the signee listed under remindersNotSentTo ("Reminder limit reached, try again later") and a reminderCooldown in seconds, not 429. The documentation previously said 429.
  • Coordinates in signatureBox and idScanBox are now also returned as decimals when stored as decimals.

Scopes

  • PATCH /docs/{documentId}/signature-field requires the write scope, in line with the scopes documented for the other endpoints that change documents.
1.5.2 2026-11-03

Account capabilities

  • GET /account/capabilities now returns aiFeaturesEnabled (false when an account admin has switched AI features off in Data controls; AI assistant settings are then refused) and aiEuOnlyProcessing (true when the account processes AI on EU-hosted models only; the AI assistant for signers is then unavailable).
1.5.1 2026-10-26

Documentation

  • The signatureType and idScanBox descriptions now state that digital_ink_id_scan places an image of the signee's identity document in the signed document, and that reproducing a copy of an identity document requires your own legal basis under Terms 8.5. No change in behaviour.
  • GET /files/{fileId}/fields and GET /templates/{templateId}/fields explain which tink-scan-id / tink-scanned-id- field names do the same, and when an MRZ text attribute on the field means no image is placed. See PDF Form Attributes.
1.5.0 2026-09-08

Public links

  • New /links endpoint group for creating and managing reusable public signing links. Anyone with the URL can open and sign the link, producing a separate document per signer. Formify does not send invitations for public links.
  • Added endpoints for listing, retrieving, updating, deleting and duplicating public links, as well as retrieving their fields and generated documents.
  • GET /links/{linkId}/documents lists completed documents created through the link. These documents can be used with the ordinary document endpoints but are not included in GET /docs.
  • Public links must be disabled with PUT /links/{linkId}/disable before deletion. Attempting to delete an active link returns 409 Conflict. Disabling a link does not affect documents already created from it.
  • Disabling is permanent, and a disabled link cannot be edited — PUT /links/{linkId} returns 409 Conflict. Duplicate the link instead.
  • Creating or duplicating a public link creates a billable public-link instance on the credits pricing model.
  • A duplicate gets its own copy of the document and its own URL, so it is independent of the link it was copied from.
  • Requires the publicLinks capability for access and publicLinksCreate for creation. Check GET /account/capabilities.

Templates

  • Templates can now be created and managed through the API with POST /templates, PUT /templates/{templateId}, DELETE /templates/{templateId} and POST /templates/{templateId}/duplicate.

Duplication and drafts

  • Added POST /docs/{documentId}/duplicate and POST /docs/drafts/{draftId}/duplicate. Both create a new draft without sending invitations or copying signature progress. Payment requirements on the source are carried over to the copy.
  • POST /docs/drafts now accepts templateId as an alternative to fileId, allowing a template to be prepared and previewed as a draft before sending.

Other changes

  • signatureBox.formFieldId is no longer part of the specification. Requests that include it are unaffected.
  • GET /templates/{templateId} returns signatureType as one of digital_ink, bankid_identification, digital_ink_id_scan, face_liveness or not_set, matching the values used elsewhere in the API. The response has its own schema in the reference.
  • Deprecated: the userId query parameter on GET /docs/drafts.
1.4.0 2026-06-24

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.
1.3.0 2026-05-26

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.
1.2.0 2026-05-06

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.
1.1.0 2026-04-21

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).
1.0.0 2026-03-27

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.
0.8.0 2026-02-04

Signing Order

  • Possibility to provide a signing order for signature requests in documents.
0.7.1 2025-06-05

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.
0.7.0 2025-04-03

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.
0.6.0 2025-02-20

Signature Fields

  • Possibility to edit contact details for signature fields not yet signed in documents sent for signing.
0.5.0 2024-12-20
  • Initial release.