Create Outbound Call
Outbound Calls
Create Outbound Call
Triggers an immediate outbound call to a phone number using the specified AI assistant
POST
Create Outbound Call
Documentation Index
Fetch the complete documentation index at: https://docs.allomia.com/llms.txt
Use this file to discover all available pages before exploring further.
Create Outbound Call
Triggers a single outbound call to a phone number using the specified AI assistant. The call is dispatched immediately upon receiving the request. Requires a tenant or organization-level API key for authentication.Headers
API key is required. Enter either your tenant-specific or organization-specific API key in the format
Bearer YOUR-API-KEYBody Parameters
Phone number to call. E.164 format is recommended (e.g.
+15145551234). Must be between 10 and 20 characters.UUID of the AI assistant to use for the call. The assistant must belong to the organization associated with the API key.
UUID of the AlloMia phone number to call from. The phone number must belong to the organization associated with the API key.
Name of the person being called. When provided, the AI assistant can use this to personalize the conversation.
Key-value pairs passed as dynamic variables to the AI assistant at call time. Values must be strings. These allow the assistant to personalize the conversation based on contextual information (e.g., patient name, appointment slot, practitioner name).
A URL to receive a
POST webhook request when the call reaches a terminal state (completed, failed, busy, or no-answer). The payload will mirror the Get Outbound Call Status response.Response
UUID uniquely identifying this outbound call record. Use this ID to poll Get Outbound Call Status and track the call’s progress.
UUID of the contact record created for this outbound call.
Initial status of the call. Always
calling on success, indicating the call has been dispatched.Human-readable description of the dispatched status (e.g.,
"Outbound call dispatched").Example Request
Example Response
Error Responses
400: Invalid request data
400: Invalid request data
Returned when the request body fails validation. The
details array lists each field-level error.401: Unauthorized
401: Unauthorized
403: Forbidden
403: Forbidden
Returned when the API key does not have the required permissions to trigger outbound calls.
404: Resource not found
404: Resource not found
Returned when the specified assistant or phone number does not exist or does not belong to the organization.
422: Organization inactive
422: Organization inactive
Returned when the organization associated with the API key is inactive.
500: Internal server error
500: Internal server error