Build custom integrations with assistants, call history, phone-number assignments, tool configuration, and provider catalogs. Every response is scoped to the API key owner and shaped by explicit DTO allow-lists.
x-api-key,api-key, or a bearer token.API keys are created in the Vomyra dashboard and must belong to an active user. Domain restrictions on the key are enforced using the request Origin or Referer header.
curl "https://docs.vomyra.com/api/v1/assistants" \
-H "x-api-key: <api-key>"{
"success": true,
"data": {},
"pagination": {
"page": 1,
"limit": 20,
"total": 42
}
}{
"success": false,
"error": {
"code": "validation_error",
"message": "name is required"
}
}OPTIONS preflight is supported. Allowed headers are Content-Type, Authorization, x-api-key, and api-key. Origins come from API_CORS_ORIGINS and default to all origins in development.
List endpoints accept page and limit. The default limit is 20 and the maximum is 100. Phone numbers are not paginated because account-level number counts are small.
Every endpoint is scoped to the API key owner and returns an explicit DTO allow-list.
Discover enum values used when configuring assistants.
Create, list, read, update, and configure tools on voice assistants.
List the authenticated user's assistants.
Create a new assistant, optionally configuring model, voice, transcription, and advanced settings.
Fetch one assistant by id.
Update one or more assistant fields.
Add a tool to an assistant's active tool list.
Remove a tool from an assistant's active tool list.
Read call summaries and detailed call transcripts.
Read owned numbers and manage assistant assignment.
Read tool instances, discover creatable types, and create API request tools.