- In Developer > Webhooks, without code.
- With the REST API, from a script or an integration platform.
- From an MCP client, with
events/subscribe. See MCP Events.
Manage webhooks in AGO
Open Developer > Webhooks to see every webhook of your workspace, whether it was created on this page, through the API or by an MCP client. Each row shows the event, its filters, the endpoint, who created it and its status:- Active: deliveries succeed.
- Failing: the endpoint fails. AGO retries the same event and holds the following ones.
- Suspended: deliveries stopped after an hour of failures.
priority = Urgent), and enter the endpoint URL. AGO checks the endpoint before saving (see Verify the endpoint). Then the webhook page shows its signing secret once: copy it into your endpoint’s configuration, as AGO cannot show it again. A webhook created here does not expire.
Click a webhook to see its status, the last error and the delivery history of the last 7 days. Resume deliveries restarts a suspended webhook from the event that failed. Delete webhook stops deliveries.
Manage webhooks with the API
Use an API key created in Developer > API Keys, or an OAuth token. A key sees and manages only the webhooks it created. To subscribe to an event, the key needs that event’s read scope, listed in the event table, such astickets:read for ticket events.
Create a webhook
A webhook is identified by your key, the event, the filters and the URL. Creating it again with the same values refreshes it and keeps its position, so no event is missed or sent twice. With a different
secret, deliveries are signed with both secrets for 24 hours, so you can switch without rejecting any. Each key can have 50 webhooks.
Errors
Receive deliveries
Verify the endpoint
When a webhook is created for a new URL, AGO first posts{ "type": "verification", "challenge": "..." }. Your endpoint must answer 200 with { "challenge": "<the same value>" }. A URL is verified once per key.
Check the signature
Every request is signed with the Standard Webhooks scheme, so its libraries work too. Check the signature on the raw body, before parsing it, and reject requests older than 5 minutes.2xx status within 5 seconds, and do the work afterwards. The MCP Events page describes the message body, the headers, the gap and terminated messages, and how retries work.
Limits
- A webhook receives one event type. Create several to receive several events.
- Events reach your endpoint about 10 seconds after they happen, in order.
- AGO retries a failing delivery for about an hour, then suspends the webhook. Nothing is lost while it is suspended, as long as you resume it within 14 days.
- The delivery history keeps 7 days.
- A webhook is deleted when the API key, OAuth access or admin account that created it is revoked, or loses the scope its event requires. AGO sends a last
terminatedmessage first. - Event data identifies what happened. Read the full object with the API or the MCP tools, such as
get_ticket. Treat event data like any API result: it can contain text written by your customers.
