SAQ does not send webhooks. There is no event subscription, no callback URL to register, no signed delivery, and no push of any kind when a ticket, comment, time entry, or period changes. If you are looking for "which webhook fires when a ticket changes", the answer is: none.
What exists instead
| Need | Use |
|---|---|
| Notice changed tickets | Poll GET /api/w/acme/tickets. The list is ordered by updatedAt descending, so page with cursor until you reach the last updatedAt you already processed. Every timeline event (field change, comment, logged time, attachment, link, viewer change, GitHub link) bumps updatedAt |
| Notice what changed on one ticket | Read GET /api/w/acme/tickets/ACME-184 and compare its events array with what you last saw; each event has a kind, an actor, a payload, and a createdAt |
| Give an assistant an overview | The MCP tool get_context_pack returns assigned, overdue, due-soon, blocked, stale, and unbilled tickets in one call |
| Tell people | Email notifications are sent to assignees, reporters, viewers, and workspace users according to each person's preference; nothing is sent to systems |
The full polling pattern, including archived tickets and rate budgeting, is in Keep an external system in sync.
Inbound
SAQ receives email through a connected mailbox (polled once a minute) and Stripe notifications for its own subscription billing. Neither is an integration point for third parties; there is no inbound webhook you can call to create or update tickets. Use POST /api/w/acme/tickets with an API token instead.