API and webhooks

Formify API and webhooks: e-signing in your own systems

Formify has a REST API with OAuth 2.0 and webhooks signed with HMAC. Your developer can send documents for signature from your own system, and you get notified when they are opened, signed or sealed.

Last updated: 17 November 2026. Reviewed by David Nordin

Key facts

Signature levelsSimple electronic signature with ink (SES), and advanced electronic signature (AES) with passport and video selfie under eIDAS
InvitationsEmail, SMS or WhatsApp
Invitation languagesEnglish, Swedish and Spanish
Signed PDFSealed with a qualified certificate from a provider on the EU Trusted List
Where data is storedDocuments and data are stored in the EU, with Sweden as the primary region (where your data is stored)
CostStart free with 10 credits per month. Top up from €10, or choose a seat from €25 per month. The MCP connection has no separate fee. Prices excl. VAT. (credits)
AuthenticationOAuth 2.0 or API key
FormatsOpenAPI, Markdown and llms.txt
Credits per sendDocuments sent through the API use credits from your Formify wallet: 2 credits for a simple signature with ink, 8 with passport and video selfie. (credits)

What you can do

  • Send the KYC form from your own client portal when a new property buyer registers.
  • Get notified the moment all parties have signed (document.completed) and file the sealed PDF in your own system.
  • Require passport and video selfie (AES) in the signing flow.
  • Prefill fields and lock them before sending, so the client only fills in their own part.
  • Read the signer's answers straight into your own system.

Webhook events

EventWhen it is sent
document.createdA document has been created and sent for signature.
document.openedThe document has been opened.
document.signedA signer has signed. The payload also includes signeeId.
document.completedAll parties have signed and the document is sealed.
document.revokedThe document has been revoked.
document.deletedThe document has been deleted.

Every event contains eventId, type, date (ISO 8601) and data with documentId, accountId and userId. Only document events are sent.

Get started

  1. Create a free Formify account.
  2. Ask your developer to read the API reference.
  3. Create credentials: OAuth 2.0, or an API key in the Formify app under Settings, Integration.
  4. Register a webhook to the address your system listens on.

Production checklist

What works, and how

What you wantStatusHow it works
Know when a document is signed or sealedNeeds a developerWebhooks document.signed and document.completed
Check that a webhook really came from FormifyNeeds a developerHMAC-SHA256 with the endpoint's whsec_ secret
Get notified without a developerWorks out of the boxIn Make, with Watch Completed Documents
Send with passport and video selfieNeeds a developerSignature type signatureFaceLiveness
Download the signed PDFNeeds a developerA time-limited link, valid for 10 minutes
Webhooks for settings or account changesNot availableOnly document events are supported
Test without production dataNeeds a developersk_test_ keys in test environments

Frequently asked questions

Does Formify have an API?

Yes. Formify has a REST API that uses JSON and OAuth 2.0 client credentials. Every tool in the Formify MCP server maps to a REST endpoint, and the reference is published as OpenAPI, Markdown and llms.txt at developers.formify.eu. For tools that can't use OAuth, you can create an API key in the Formify app under Settings, Integration.

Which webhook events does Formify send?

Six, all about documents: document.created, document.opened, document.signed, document.completed, document.revoked and document.deleted. Each webhook is signed with HMAC-SHA256 using a secret unique to the endpoint, so your system can check that it came from Formify. You can rotate the secret when you need to.

What happens if our server is down when a webhook is sent?

Formify tries again up to five times: right away, then after about 5 minutes, 30 minutes, 2 hours and 24 hours. Your server confirms delivery with a 2xx response. An event can arrive more than once or out of order, so your developer should use the eventId to skip duplicates.

Can we add identity verification through the API?

Yes. With the signature type signatureFaceLiveness, the signer scans their passport and records a video selfie before signing. That gives an advanced electronic signature (AES) under eIDAS. For a simple signature with ink, use digital_ink.

We don't have a developer. What can we do?

Use Make. The Formify app on Make has ready-made modules, such as Watch Completed Documents, which starts a scenario when a document is completed, so you can act on signed documents without writing code. To send and follow up from the chat instead, connect Formify to ChatGPT or Claude.

How is this page different from the developer documentation?

This page explains what you can build with the Formify API and webhooks, and what it takes. API documentation and the API reference are written for developers, with every endpoint, parameter and code example.