TuCloudAPI getagentlookups
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
Dropdown data for the agent screens: this PBX's queues (assign an agent to a queue) and its extensions {_id,num,name}. The front sends ext_id on a write; addagent derives the member's membername (Agent/<sipuser>), interface (SIP/<sipuser>) and name server-side.
Call
https://tucloudapi.7kas.com:9087/tucloud?func=getagentlookups&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 (tenant boundary). |
Example
https://tucloudapi.7kas.com:9087/tucloud?func=getagentlookups&ukey=KEY&pbx=tucall
Response
{ok, queues:[{_id,label}], extensions:[{_id,num,name}]}.
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