Service workspace
Use the top service tabs to open the guided view for carriers, DIDs, AI, calling teams, messaging, leads, or meetings.
Browse service areas →SYSTEM INTEGRATIONS
Use the Kazitel panel for day-to-day setup. Add an API connection only when another business system needs to exchange data with your account.
ACCESS TOKENS
Loading…
ACCESS AND AUTHENTICATION
Create one access token per service under Access tokens above. A token reaches only its own service, with the access of the account that made it.
Use a service access token. Keep it in your backend secret manager.
Authorization: Bearer $KAZITEL_API_TOKEN
Accept: application/jsonUse the tenant’s dedicated SMS key. Account activation, allowed IPs, rate limits, balance, and recipient limits still apply.
X-Api-Key: $KAZITEL_SMS_API_KEY
Content-Type: application/jsonThe capture source is separate from an administrator token and has its own origin controls.
POST /tenant-api/leads/capture/{key}Set the verified HTTPS panel origin and tenant token in server-side environment settings.
const baseUrl = process.env.KAZITEL_API_BASE_URL;
const token = process.env.KAZITEL_API_TOKEN;
if (!baseUrl || !token) throw new Error('Set API base URL and tenant token');
const response = await fetch(new URL('/tenant-api/pbx/call-center-queues', baseUrl), {
headers: { Authorization: `Bearer ${token}`, Accept: 'application/json' },
});
if (!response.ok) {
const detail = await response.text();
throw new Error('Kazitel API ' + response.status + ': ' + detail.slice(0, 500));
}
const queues = await response.json();
console.log(queues);Use the exact payload fields accepted for the tenant account.
const response = await fetch(new URL('/tenant-api/broadcast/sms/send', process.env.KAZITEL_API_BASE_URL), {
method: 'POST',
headers: {
'X-Api-Key': process.env.KAZITEL_SMS_API_KEY,
'Content-Type': 'application/json',
Accept: 'application/json',
},
body: JSON.stringify({ /* use the tenant's validated SMS payload */ }),
});
if (!response.ok) throw new Error('SMS API returned ' + response.status);LIVE UPDATES
The deployed app does not publish customer-authorized WebSocket events for calls, agent presence, or campaign delivery yet. Use the supported REST resources while tenant event access is prepared.
GET /tenant-api/pbx/gatewaysCustomer REST API
GET /api/v1/dids/catalogCustomer REST API for IVR, dialplans, recordings, extensions, and ring groups; DID inventory remains panel-managed.
GET /tenant-api/pbx/ivr-menusCustomer IVR REST API; AI runtime bridge is internal-only.
GET /tenant-api/pbx/call-center-queuesCustomer REST API
POST /api/sms/v1/sendCustomer REST API
GET /api/v1/portal/crm/tasks/domainsTenant CRM task REST API; call-control bridge remains internal.
POST /api/lead-gen/capture/{key}Customer REST API
POST /api/lead-gen/capture/{key}Lead capture and contacts are available; no native store connector API was verified.
GET /tenant-api/pbx/gatewaysCustomer REST API
GET /tenant-api/pbx/ivr-menusCustomer REST API for IVR menus, recordings, extensions, and ring groups; AI runtime bridge is internal.
GET /tenant-api/pbx/conference-roomsCustomer REST API
MACHINE-READABLE REFERENCE
Verified customer routes only; internal bridge routes are excluded.
Schema format: OpenAPI 3.2.1.