Webhooks
Webhooks
Webhooks push real-time notifications from Atlas to your own endpoints the moment something happens in a workspace. Every delivery is signed, can be checked against replay, and is retried on a fixed schedule when it fails.
What are webhooks
A webhook turns Atlas into a push producer. Instead of polling the API on a timer to discover changes, you register an HTTPS endpoint once, and Atlas sends it a small signed JSON payload whenever a subscribed event occurs.
Reach for webhooks when you need to react to work as it happens: kick off a build when a task completes, sync a record into your data warehouse when a project closes, post to a channel when a goal is met. Polling wastes requests and adds latency; a webhook arrives within seconds and carries exactly the change that triggered it.
New here? Start with the Quickstart
How delivery works
Every webhook rides the same path from an event in your workspace to your endpoint.
When an event happens in your workspace, Atlas signs the payload and sends it over HTTPS to your endpoint, retrying on a fixed schedule when a delivery fails.
- 1. An event happens. An action is recorded in your workspace, for example a task is completed or a project is created.
- 2. Atlas matches subscriptions. The event is checked against every enabled webhook in your workspace using its event patterns.
- 3. Atlas signs and sends. A JSON event is signed with your webhook secret and sent in a POST request over HTTPS to your endpoint, with headers that let you verify it and detect replays.
- 4. Your endpoint verifies and acts. You check the signature and timestamp, return a 2xx quickly, and process the event.
- 5. Failures retry automatically. A server error, a timeout, or a network error is retried up to eight attempts in total, and every attempt is recorded in your delivery log.
Explore the guide
Each page below goes deep on one part of the system.
- QuickstartCreate a subscription, receive your first event, verify it, and go live.
- EventsWhich events you can subscribe to and how exact, prefix, and wildcard matching work.
- Payloads and headersThe exact JSON envelope and every header sent on a delivery, with a worked example.
- Security and signingVerify signatures, defend against replays, rotate keys, and handle secrets safely.
- Delivery and retriesThe retry ladder, delivery history, replays, test deliveries, and idempotency.
- Managing via APICreate, list, update, and rotate webhooks over the REST API, with scopes and roles.