Authenticate
Send your admin credentials to Save the cookie jar (the
POST /api/admin/login. On success the server sets a session cookie that authenticates all subsequent requests.-c cookies.txt flag in cURL) and pass it with every subsequent request using -b cookies.txt.If the credentials are wrong the API returns HTTP 422 with
"message": "Invalid credentials.". Double-check the email and password and retry.Create a tenant
A tenant represents one customer organisation on your platform. Every resource — extensions, DIDs, queues — belongs to a tenant. Send Note the
POST /api/tenants with the required fields.id returned in the response — you will use it as tenant_id in the next step.Both
slug and domain must be unique across all tenants. The API returns HTTP 422 with validation errors if either value is already taken.Add an extension
Provision a SIP extension for the tenant. The
extension_number is the diallable short code, and secret is the SIP registration password for the endpoint device.What’s next
You now have an authenticated session, a tenant, and a live extension. From here you can:- Assign a DID — send
POST /api/didsto assign a direct inward dialing number to the tenant and route it to the extension. - Create a call queue — send
POST /api/queuesto build an ACD queue and add the extension as an agent. - Configure SMS — send
POST /api/sms-gatewaysto attach an SMS gateway to the tenant, then usePOST /api/sms-gateways/{smsGateway}/sendto send messages.