Skip to main content
AmDital sends an HTTP POST to your endpoint when a subscribed event happens in your workspace. Each request is signed with a secret that you choose, so your receiver can prove the request came from AmDital and was not replayed.

Register a webhook

From the app

1

Open the Webhooks page

As a workspace Owner or Admin, go to Settings → Developer, then open the Webhooks card.
2

Add an endpoint

Click Add Webhook. Enter a name, your endpoint URL, a Signing Secret, and select at least one event. Then click Create.
3

Check deliveries

Expand a webhook in the list to see its delivery history (status, HTTP code, latency) for each attempt.
The event checklist in the app offers 21 of the 35 event types (projects, deals, the ticket.created/updated/deleted events, invoices, leads, and expenses). To subscribe to the contact.*, task.*, or the other ticket.* events, register the webhook through the API.

From the API

POST /api/v1/webhooks requires a session bearer token (see Authentication) for a member whose role has the integrations.webhooks.create permission. By default that is the Owner, Admin, and Manager roles.
Update or remove a webhook with PATCH /api/v1/webhooks/{id} and DELETE /api/v1/webhooks/{id}. List them with GET /api/v1/webhooks. The signing secret is returned only to Owner, Admin, and Manager roles; other members see null.

Event types

The platform defines these 35 event types:

Request format

Each delivery is a POST with a JSON body:
The fields inside data depend on the event. Headers sent with each delivery:

Verify the signature

v1 is the hex HMAC-SHA256 of the string ${t}.${rawBody}, keyed with your signing secret. t is the Unix time (seconds) when the request was signed. Reject requests whose t is more than 5 minutes (300 seconds) from your clock to block replays. Always compute the HMAC over the raw request body bytes, before any JSON parsing.

Delivery and retries

  • Respond with any 2xx status to acknowledge. Any other status, a redirect (3xx responses are not followed), or no response within 30 seconds counts as a failed attempt.
  • Each delivery gets 3 attempts in total: the first try, then retries roughly 10 seconds and 20 seconds later (exponential backoff). After the third failed attempt the delivery is marked failed.
  • Every attempt is recorded in the webhook’s delivery history in Settings → Developer → Webhooks.
  • A paused or deleted webhook stops receiving deliveries, including pending retries.