TuCloudAPI getqueues
TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: SuperRoot, Operator, Client.
pbx parameter (the PBX name, e.g. tucall). The server verifies that your ukey's own account owns that PBX, whatever its role; otherwise, and also for a PBX that does not exist, it returns {"ok":false,"code":"forbidden"}.Description
List the PBX call queues (ACD) with member counts. Tenant from (ukey, pbx).
Call
https://tucloudapi.7kas.com:9087/tucloud?func=getqueues&ukey=YOUR_KEY&pbx=PBX_NAME
GET, or POST with the parameters form-urlencoded in the body. Requires the ukey parameter. Always HTTP 200; the response is a JSON envelope.
Parameters
| Parameter | Type | Required | Default | Meaning |
|---|---|---|---|---|
pbx |
string | Yes | — | FuturePBX NAME (e.g. tucall). The (ukey, pbx) pair is the tenant boundary; the server verifies the ukey owns this PBX. |
q |
string | No | — | Optional title search (contains). |
Example
https://tucloudapi.7kas.com:9087/tucloud?func=getqueues&ukey=KEY&pbx=tucall
Response
{ok, rows:[{_id,title,name,exten,strategy,hash_presence,member_count}]}. hash_presence = the queue's presence key md5(name || hash16) for the live monitor (empty when the PBX has no hash16).
Errors
Always HTTP 200. On failure the body is {"ok":false,"code":"...","message":"..."}. Common codes: missing_pbx, forbidden, invalid_param, not_found, conflict, in_use, db_error, server_busy; the Response section above lists any specific to this function.
Back to TuCloudAPI