Customisation and integrations

API tokens and webhooks

Connect other systems with API tokens limited to what they need, and signed webhooks.

Integrations with sensible limits

Create API tokens with separate read and write scopes for each integration, and send signed webhooks to other systems. Check delivery attempts, and failed deliveries retry automatically. Tokens can’t touch billing, sign-in or secrets.

  • Connect your website or other systems
  • Send events to another tool when things change
  • Give each integration only the access it needs

How it works

  1. Create a token

    Choose read or write access for the areas the integration needs.

  2. Set up webhooks

    Send signed notifications to another system when events happen.

  3. Monitor

    Check delivery history; failed deliveries retry.

Sending won deals to accounting

A business sends a webhook to its accounting integration when a deal is won, using a token limited to the Revenue area.

Good to know

  • API access is on Professional plans and above.
  • Tokens can’t change billing, sign-in or integration secrets.

Questions about API tokens and webhooks

More answers on the questions page.

Are webhooks signed?

Yes. Outbound webhooks are signed so the receiver can verify them.

Can we limit a token to read-only?

Yes. Read and write scopes are separate.

Start with the customers you already have.

Free for up to two people, with no card needed. Upgrade when you need service, projects or automation.