Skip to main content

Voice AI Public APIs

Voice AI Public APIs give developers programmatic access to Voice AI agents, actions, call data, transcripts, and external integrations.

What Voice AI Public APIs Do

Voice AI Public APIs extend Voice AI beyond the Kyrios interface. They allow developers to build around Voice AI instead of managing every task manually inside the platform.

Common API use cases include:

  • Agent setup and updates

  • Action management

  • Call log retrieval

  • Transcript retrieval

  • Webhook-based integrations

  • External reporting and automation


Where to Find Voice AI Agents

Go to AI Agents, then open the Voice AI tab. Use the Agent List tab to view existing Voice AI agents.

Manage Agents and Actions

Voice AI Public APIs can help teams manage agents and actions at scale.

Use API-based agent management when you need a standardized setup process across multiple agents or locations.


Voice AI agents can also be configured in the Kyrios interface with prompts, knowledge bases, actions, numbers, and availability settings.

Retrieve Call Data

Voice AI Public APIs can retrieve call logs and transcripts.

Use retrieved call data for:

  • Call quality review

  • Reporting dashboards

  • Compliance records

  • Conversation analysis

  • CRM enrichment

  • Follow-up automation

The Dashboard & Logs area shows Voice AI performance data, including attempted calls, connected calls, actions triggered, sentiment, and unattempted calls.

Use Voice AI With Workflows and Webhooks

Voice AI data can support workflow automation and external system updates.

Use webhook-based workflows when Voice AI activity needs to be sent to another app, database, CRM, or internal tool.

Voice AI Public APIs, workflow webhooks, and Voice AI Custom Actions are related, but they are not the same feature.

  • Voice AI Public APIs provide programmatic access to Voice AI capabilities.

  • Workflow webhooks send workflow data to external systems.

  • Voice AI Custom Actions are used for real-time integrations during live calls.

Use Private Integrations for Secure Internal Connections

Use Private Integrations when your team needs a secure connection between Kyrios and an internal system.

Private Integrations are useful when building authenticated internal tools, custom reporting systems, or controlled API workflows.

Knowledge Base and Future API Capabilities

Voice AI agents can already use a configured knowledge base inside Kyrios.

Knowledge Base support through the Actions API is a future API capability and should not be treated as currently released unless official API documentation confirms it.

The same applies to any future Voices API capability for retrieving available voices and voice details.


How to Set Up Voice AI Public APIs

  1. Confirm that Voice AI is enabled and agents are already configured in Kyrios.

  2. Review what your integration needs to do.

  3. Decide whether you need agent management, transcript retrieval, call logs, webhooks, or live-call actions.

  4. Open the official API documentation for authentication, endpoint details, rate limits, and implementation requirements.

  5. Use Private Integrations when connecting Kyrios to an internal system.

  6. Build and test in a controlled environment.

  7. Validate that call data, transcripts, webhook events, or agent updates work as expected.


Common Issues and Fixes

The API use case overlaps with Custom Actions

Use Voice AI Custom Actions for real-time live-call behavior. Use Voice AI Public APIs for broader programmatic access, data retrieval, and external integrations.

Call data is not available in an external system

Confirm that the integration is retrieving the correct call logs or transcript data. Also, confirm that authentication and permissions are configured correctly.

A webhook is not firing

Check the workflow action setup, webhook URL, method, headers, and payload configuration.

FAQ

What can I do with Voice AI Public APIs today?

Voice AI Public APIs can support agent and action management, call log retrieval, transcript retrieval, and webhook-based integrations.

Does this article replace the official API documentation?

No. This article explains the feature and setup path. The official API documentation is the source for authentication, endpoint details, rate limits, and implementation requirements.

Is Knowledge Base support through the Actions API already available?

Knowledge Base support through the Actions API is described as a future capability. Current Voice AI knowledge base assignment is available through the existing Voice AI setup experience.

Are Voice AI Custom Actions the same as Voice AI Public APIs?

No. Voice AI Custom Actions are for real-time webhook integrations during live calls. Voice AI Public APIs provide broader programmatic access to Voice AI capabilities and data.

Can I use Voice AI call data in automations?

Yes. Voice AI call data and transcripts can support automations, reporting, QA, and external workflows.

Where should developers start?

Developers should start with the official API documentation, then use Private Integrations when building secure internal connections.

Did this answer your question?