TuCloudAPI addroute: Difference between revisions
API docs (generated from func=help) — add #48 adminusers + #52 pbxconfig |
TuCloudAPI reference: product name -> FuturePBX (API surface unchanged); regenerated from func=help |
||
| Line 1: | Line 1: | ||
''TuCloudAPI function to manage | ''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.'' | ||
== Description == | == Description == | ||
Revision as of 14:13, 3 August 2026
TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: SuperRoot, Operator, Client.
Description
Create an inbound route (header only; add steps with addroutestep). Server derives tucloudpbx_id + root. Requires a non-readonly ukey.
Call
GET https://tucloudapi.7kas.com:9087/tucloud?func=addroute&ukey=YOUR_KEY
Requires the ukey parameter.
Parameters
| Parameter | Type | Required | Default | Meaning |
|---|---|---|---|---|
pbx |
string | Yes | — | TuCloud PBX NAME (e.g. tucall). The (ukey, pbx) pair is the tenant boundary; the server verifies the ukey owns this PBX. |
name |
string | Yes | — | Route name (required, max 32). |
nota |
string | No | — | Optional note (max 256). |
ref_id |
integer | No | 0 |
Optional grouping reference (0 = none). |
Example
https://tucloudapi.7kas.com:9087/tucloud?func=addroute&ukey=KEY&pbx=tucall&name=Horario
Response
{ok, route:{_id,name,nota,ref_id}}.
Back to TuCloudAPI