TuCloudAPI getextqr
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
SIP provisioning QR for one extension, rendered server-side to a PNG (base64). The SIP password is embedded ONLY inside the QR bitmap — it is never returned as plaintext JSON. transport/proxy are resolved server-side from the authoritative SIP config. Send-to (TOEXT) extensions have no registrable account -> {ok:false,not_registrable}.
Call
https://tucloudapi.7kas.com:9087/tucloud?func=getextqr&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 | — | Extension id (_id). |
Example
https://tucloudapi.7kas.com:9087/tucloud?func=getextqr&ukey=KEY&pbx=tucall&id=87365
Response
{ok, png:"<base64 PNG>", sipaccounts:[{sipusername,transport,subdomain?}]} (no password in JSON).
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