API Changelog
Changes to the Envocal API, newest first. Within v1, changes are backward compatible.
The Envocal API
Run Envocal from your own systems with the new public API. Create customer tenants, set them up with agents (also from templates), knowledge bases and phone numbers, invite their users, and read conversations and usage for your reporting and billing. One API key reaches your tenant and all your customers.
Start with the API Reference. The whole API is also one OpenAPI spec: give it to your AI coding agent and it has every endpoint, parameter and response it needs.
API keys in the Vault
Tenant admins create API keys under Vault → API keys: full access, read only, or custom permissions per area, so a billing report can read usage and nothing else. Keys can expire, be edited and be revoked at any time. See API keys.
Data region for tenants
Every tenant now has a data region: where its data is stored. You choose it when you create a tenant (it starts as the parent's), and the tenant's Details tab shows it. Today the only region is EU; API keys carry it (
evk_eu_…), and creating a tenant through the API takes it asregion. See Data region.
API Reference
Provision tenants, agents, knowledge bases and phone numbers, and read conversations and usage, from your own systems.
Identify the caller GET
The API key you are calling with and its tenant. Start here: tenantId is what current stands for in /v1/tenants/current/..., and GET /v1/tenants lists that tenant with all its sub-tenants. Works with any valid key, whatever its permissions.