Agent Webhooks
In addition to the project-level default webhook, you can configure individual webhook endpoints for each agent. When a per-agent webhook is set, it overrides the project default for that agent’s events — the event is delivered to exactly one endpoint, never both.
This is useful when you have multiple agents and want to route their events to different backend services or processing pipelines.
How it works
When an event occurs (e.g., an inbound message to an agent’s number):
- If the agent has its own webhook configured, the event is delivered only to the agent’s webhook
- If the agent does not have its own webhook, the event is delivered to the project default webhook
Events are never duplicated across both endpoints. Per-agent webhooks use the same payload format and signature verification mechanism described in the Webhooks guide.
Create or update agent webhook
Register or update a webhook URL for a specific agent.
Request body
A new signing secret is generated each time you create or update a webhook. Save the secret value from the response.
Example
Get agent webhook
Get the webhook configuration for a specific agent. Returns null if no webhook is configured.
Example
Delete agent webhook
Remove the webhook for a specific agent. Events will revert to being delivered to the project default webhook after deletion.
Example
Agent webhook deliveries
View recent delivery attempts for a specific agent’s webhook.
Query parameters
Example
Test agent webhook
Send a test webhook to verify the agent’s webhook endpoint is working correctly.
