Skip to main content
The reference documents Athena’s hosted customer API: agents, calls, campaigns, model configurations, telephony configuration, tools, knowledge documents, website sessions, and reporting. The request fields are checked against the running API’s OpenAPI schema. Authentication metadata is clarified from the actual route dependencies because the runtime schema does not describe every custom API-key check. Administrative metrics, platform-superuser operations, provider callback handlers, and internal voice-worker operations are outside this customer reference. An organization administrator is different from a platform superuser. Retry Review’s staff-only star-management and golden-case export routes are not customer API operations.

​
Stable integration choices

Use public call-trigger endpoints to initiate phone calls from your backend. Dashboard management endpoints serve resource configuration; their availability still depends on account permissions and feature settings. Use exact field names from the schema. Some integration identifiers and headers retain legacy names for compatibility, even though the hosted product is Athena.

​
Validation versus runtime

A documented schema describes accepted fields. It does not guarantee that a configured external provider is reachable or that a call will complete. Follow the run verification stages when checking an integration end to end. The reference is read-only. Run examples from your backend with your own API key and synthetic test resources. Calls, tool tests, campaign actions, and text sessions perform real work.

​
Feature prerequisites

Use the guides for each feature’s setup and lifecycle, including Athena capabilities, Models, Tools and knowledge, and Website embedding.