Jump to content

TuCloudAPI getqueue

From Wiki 7Kas

TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: SuperRoot, Operator, Client.

ℹ Requires the 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

Get one queue's config. music_id is the tucloud_pbx_music id for the MOH class. ringinuse 0/1 = whether agents already on a call are rung (default 0 since 2026-10-31). 404-style not_found if not in the caller's PBX.

Call

https://tucloudapi.7kas.com:9087/tucloud?func=getqueue&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.
id integer Yes — Queue id (_id).

Example

https://tucloudapi.7kas.com:9087/tucloud?func=getqueue&ukey=KEY&pbx=tucall&id=1001

Response

{ok, queue:{_id,title,name,exten,strategy,timeout,retry,wrapuptime,maxlen,joinempty,leavewhenempty,ringinuse,musiconhold,music_id,weight,servicelevel,desvio,hash_presence}}.

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