Webhook Technical Specifications

Endpoint


POST https://api.dialora.ai/webhooks/agents/{agentWebhookId}/trigger

{agentWebhookId} is unique to each agent. Find it under Advanced Settings → Call Management — see Finding Your Webhook URL.

Method


POST

Content type


application/json

Required headers


{
  "Content-Type": "application/json"
}

There is no separate auth header. The webhook ID in the URL is the credential — treat the whole URL as a secret.

Request body

Field	Type	Required	Notes
`phone`	string	Yes	E.164, e.g. `+14155550132`
`name`	string	Yes	Callee’s name. `full_name` or `fullName` satisfies this instead.
`full_name`	string	—	Alias for `name`
`fullName`	string	—	Alias for `name`
`email`	string	No	Must be a valid email if supplied

A request with no name, full_name, or fullName is rejected with 400 Bad Request and the message name or full name is required.

Any other keys you send are kept and passed to the agent as context for that call — see Essential Data Fields.


{
  "phone": "+14155550132",
  "name": "John Doe",
  "email": "john.doe@example.com"
}

Behaviour

The call is placed by the agent that owns the webhook, using its published version.
The agent’s assigned phone number is used as the caller ID.
The request returns once the call has been queued — it does not wait for the call to finish.
Each request places one call. There is no built-in deduplication, so a retry places a second real call.

Limits

Calls consume account credits. A request with no available balance won’t place a call.
Pace your requests rather than bursting — see Best Practices.

The Calls API gives you scoped API keys, per-call variables, your own metadata echoed back, and a signed completion webhook you can verify. Use it for anything beyond a simple no-code trigger.