Webhooks

Outgoing webhooks

Formality notifies your systems when contracts, entities, contacts, documents, users or custom object records change, by sending signed HTTPS messages to the endpoints you configure.

How it works

Administrators create webhook endpoints in the Interoperability settings, with an HTTPS URL and the events to subscribe to, such as agreement.updated, entity.created or document.downloaded. Wildcards like agreement.* are accepted.

Each message is signed with an HMAC secret so the receiver can check it comes from Formality. When the secret is rotated, the old one remains valid for seven days so the receiver can switch over.

Failed deliveries are retried. After five consecutive exhausted deliveries the endpoint is disabled and administrators are notified. Deliveries can be followed and replayed from the monitoring screen.

What you get

  • Create, update and delete events
  • Document view and download events
  • Signed payloads with secret rotation
  • Retries and automatic disabling

Why teams use it

Real-time sync

Your ERP or procurement tool learns about a change as it happens.

Status updates downstream

Push contract status and signature events to your business tools.

Secure by design

Signed messages over HTTPS only.

Reliable delivery

Retries, replay and alerts when an endpoint fails.

More in Integrations & API

See all →

MCP server and API for AI agents

Connect Claude, ChatGPT or Copilot to your contracts, within your rules.

Learn more →

REST API

Create and update contracts, entities and documents from your tools.

Learn more →

Microsoft Teams

Notifications and reminders in Teams.

Learn more →

Slack

Notifications and reminders in Slack.

Learn more →