Receiving event webhooks
Subscribe to deploys, alerts, and billing events.
3 min read
Webhooks let your systems react to platform events without polling. Configure one at /dashboard/account → Webhooks → New endpoint.
Supported events: `service.created`, `service.destroyed`, `service.alert`, `deploy.succeeded`, `deploy.failed`, `invoice.paid`, `invoice.failed`, `ticket.replied`. Subscribe to all or a subset.
Payload: JSON with `event`, `created_at`, and a typed `data` envelope. Signed with HMAC-SHA256 using the secret we generate at endpoint creation; verify the `X-Vintony-Signature` header in your handler.
Retry policy: failed deliveries retry with exponential backoff for 24 hours. Each retry shows in the dashboard; you can replay any past event manually.
Best practice: respond with 2xx within 5 seconds. Long work belongs in a queue; the webhook receiver just enqueues. Slow webhooks cause platform back-pressure and eventual disablement.