Webhooks

What is a webhook?

A webhook is a way for Astalty to notify another system the moment something happens in your account — automatically, without that system having to constantly ask.

The difference is who starts the conversation:

• With the API, your system asks Astalty for information ("give me the list of participants").
• With a webhook, Astalty tells your system when something changes ("a participant was just created").

You give Astalty a URL (an "endpoint" on your own server). When a relevant event happens — say a new task is created — Astalty sends an HTTP POST request to that URL with a small JSON payload describing what happened. Your system receives it and can react: update a record, send a notification, kick off a workflow, and so on.

Why use webhooks?

Webhooks let you build real-time, event-driven integrations without polling the API on a schedule. Instead of repeatedly checking "has anything changed yet?", your system simply waits to be told. This is faster, uses fewer API calls, and keeps other systems in sync with Astalty as changes happen.

How webhooks work in Astalty

1. You create a webhook in the API Dashboard, giving it a URL and choosing which events it should listen for. See Setting up a webhook.
2. When one of those events happens, Astalty sends a signed POST request to your URL with details of the event.
3. Your endpoint verifies the signature and responds with a 2xx status to confirm it was received.
4. If your endpoint can't be reached or returns an error, Astalty automatically retries on a back-off schedule.

Next steps

• Supported webhook events — the full list of events you can subscribe to.
• Setting up a webhook — create and manage webhooks in the API Dashboard.
• Receiving and verifying webhooks — payload format, signature verification, retries and delivery logs.