Skip to main content
Leamout’s customer-facing HTTP operations are versioned under /v1 and normally return JSON. The API reference covers organization-token operations for Voice Agents, AI integrations, tools, SIP trunks, numbers, calls, recordings, storage, network and retention policies, audit events, webhooks, plans, and usage. Console account administration is intentionally outside the developer API reference. Organization-owned API operations require a scoped bearer credential. The public plans listing does not require a token. Example:
Successful JSON responses are wrapped as:
Error responses use success: false and an error object. Some successful mutations return 204 No Content. A trailing slash is part of several collection routes (such as /v1/voice-agents/); use the documented route spelling.
The OpenAPI catalog documents verified public routes and key request shapes. Endpoint-specific response fields and status codes should still be checked against the API, especially where a schema is intentionally left generic.