Subscribe to Daytona webhooks to react to sandbox, snapshot and volume lifecycle events

Documented steps

1. Confirm your role first: webhooks are available to organization admins and members with the appropriate permission.
2. In the Daytona Dashboard, click Webhooks in the sidebar, then Add Endpoint.
3. Give the endpoint a name and an HTTPS receiver URL.
4. Subscribe to the sandbox events you need: `sandbox.created` (a new sandbox has been created) and `sandbox.state.updated` (a sandbox's state has changed).
5. Add related resource events from the same catalog if relevant: `snapshot.created`, `snapshot.state.updated`, `snapshot.removed`, `volume.created`, `volume.state.updated`.
6. Save the endpoint, then trigger a real lifecycle change (create a sandbox, stop it) to produce a test delivery.
7. Inspect deliveries and their status in the endpoint's Messages tab in the dashboard.
8. Parse the JSON payload in your receiver and branch on the state field — `sandbox.state.updated` is a single generic event, not one event per transition.
9. Make the receiver idempotent and tolerant of duplicate or out-of-order deliveries, since retry semantics are not specified in the docs.
10. Treat the webhook as a trigger to re-read authoritative state via the API rather than as the source of truth. Official docs: https://www.daytona.io/docs/en/webhooks