Jump to content

TuCloudAPI setprofileapps: Difference between revisions

From Wiki 7Kas
API docs (generated from func=help) — setprofileapps wording fix
TuCloudAPI reference: product name -> FuturePBX (API surface unchanged); regenerated from func=help
Line 1: Line 1:
''TuCloudAPI function to manage tucloud (PBX) services. Available to: '''SuperRoot, Operator, Client'''.''
''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.''


== Description ==
== Description ==

Revision as of 14:14, 3 August 2026

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

Description

Bulk-save a profile's FULL permission matrix in one call (the primary matrix write). matrix = a JSON array of {app_name, access, insert, delete, update, export, print} (flags 0/1) that MUST cover every catalog app — an incomplete or empty matrix is rejected (invalid_param), so a partial body can never leave stale permissions; extra unknown app_names are ignored. app_type-irrelevant privileges are normalised to 0 server-side. Send via POST body. not_found if the profile is not in this PBX. Requires a non-readonly ukey.

Call

GET  https://tucloudapi.7kas.com:9087/tucloud?func=setprofileapps&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 and scopes every profile to it.
group integer Yes Profile id (_id).
matrix string Yes JSON array of per-app permission rows (see description).

Example

https://tucloudapi.7kas.com:9087/tucloud?func=setprofileapps&ukey=KEY&pbx=tucall&group=1  (matrix in POST body)

Response

{ok, apps:[...]} or {ok:false,code:not_found|invalid_param}.


Back to TuCloudAPI