Webhooks

Open Settings → Integrations → Webhooks to configure outbound webhook destinations. Each webhook is bound to an API key and delivers signed events to your target URL. This page is where you create, list, and delete webhooks and copy secrets and tokens.

The list

• Event type — the subscribed type or family umbrella

• Target URL — the HTTPS destination

• API key — the bound key as name (prefix…)

• Token — the filter token, masked until you Reveal; then Hide or Copy

Manageable rows also show Delete. Filters for Event type, Target URL, and API key narrow the list.

Create a webhook

Click Create Webhook. In the dialog:

1. Event type — pick a fine-grained type (for example task.state_changed) or a family umbrella (for example task)

2. API key — pick a key that holds the required read grant for that event's family. Keys missing the grant are labeled accordingly and cannot be selected

3. Target URL — an HTTPS URL that will receive signed event POSTs

Click Create Webhook. An organization may hold up to 25 active webhooks for any one event family.

After creation

The Webhook Created dialog shows three values:

• Signing secret — begins with whsec_. Shown only this once. Use it in code to verify Standard Webhooks signatures.

• Header name — always x-abletime-token

• Header token — a reusable filter token for no-code tools. You can Reveal and Copy it again from the list.

The dialog also includes Receiver setup tips for Make (enable Get request headers, then filter on x-abletime-token). For Zapier notes, see Guides → Connecting Make. Also see Guides → Receiving Webhooks.

Delete a webhook

Click Delete, then confirm in Delete Webhook. The destination stops receiving events immediately.

Delivery contract

Envelope shape, event types, headers, signature verification, and retries are documented under Documentation → API → API Webhooks. Registration, secrets, and token management stay on this Settings page.