TuCloudAPI updateadminuser: Difference between revisions
API docs (generated from func=help) — #48 rescoped to per-PBX |
TuCloudAPI reference: portal users email + magic link (generated from func=help) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
''TuCloudAPI function to manage | ''TuCloudAPI function to manage FuturePBX (the cloud PBX). Available to: '''SuperRoot, Operator, Client'''.'' | ||
{{Note|1=Requires the <code>pbx</code> parameter (the PBX '''name''', e.g. <code>tucall</code>). The server verifies that your <code>ukey</code>'s own account owns that PBX, whatever its role; otherwise, and also for a PBX that does not exist, it returns <code>{"ok":false,"code":"forbidden"}</code>.}} | |||
== Description == | == Description == | ||
Edit a portal | Edit a portal user in THIS PBX: name, active, priv_admin, role and phone are replaced as sent; disable_2fa=1 turns 2FA off and clears the secret (never enables). The password and the email are never changed here: a non-empty password is refused (field password, reason not_allowed); an email that is absent, empty, the confirmed address or the open one is ignored (a form re-posting the record never fails and never mails), a DIFFERENT one is refused (field email, reason not_allowed): the email changes with requestadminuseremail. A refusal writes nothing. tucloudpbx_id and root are NEVER changed. not_found if the login is not in this PBX. Requires a non-readonly ukey. | ||
== Call == | == Call == | ||
https://tucloudapi.7kas.com:9087/tucloud?func=updateadminuser&ukey=YOUR_KEY&pbx=PBX_NAME | |||
Requires the <code>ukey</code> parameter. | GET, or POST with the parameters form-urlencoded in the body. Requires the <code>ukey</code> parameter. Always HTTP 200; the response is a JSON envelope. | ||
== Parameters == | == Parameters == | ||
| Line 12: | Line 14: | ||
! Parameter !! Type !! Required !! Default !! Meaning | ! Parameter !! Type !! Required !! Default !! Meaning | ||
|- | |- | ||
| <code>pbx</code> || string || Yes || — || | | <code>pbx</code> || string || Yes || — || FuturePBX NAME (e.g. tucall). The (ukey, pbx) pair is the tenant boundary; the server verifies the ukey owns this PBX and scopes every admin user to it. | ||
|- | |- | ||
| <code>login</code> || string || Yes || — || | | <code>login</code> || string || Yes || — || The user's _id (login). A new user's is generated by the server and never shown. | ||
|- | |- | ||
| <code>email</code> || string || | | <code>email</code> || string || No || — || Ignored when absent, empty, the current or the open address; any other value is refused. | ||
|- | |- | ||
| <code>name</code> || string || No || — || Display name. | | <code>name</code> || string || No || — || Display name. | ||
| Line 33: | Line 33: | ||
|} | |} | ||
== Example == | == Example == | ||
<nowiki>https://tucloudapi.7kas.com:9087/tucloud?func=updateadminuser&ukey=KEY&pbx=tucall&login= | <nowiki>https://tucloudapi.7kas.com:9087/tucloud?func=updateadminuser&ukey=KEY&pbx=tucall&login=u0123456789abcdef&name=Ana&active=1</nowiki> | ||
== Response == | == Response == | ||
{ok, user:{...}} | {ok, user:{...}, status, email_pending, expires_in} | {ok:false, code, field?, reason?, message}. | ||
== Errors == | |||
Always HTTP 200. On failure the body is <code>{"ok":false,"code":"...","message":"..."}</code>. Common codes: <code>missing_pbx</code>, <code>forbidden</code>, <code>invalid_param</code>, <code>not_found</code>, <code>conflict</code>, <code>in_use</code>, <code>db_error</code>, <code>server_busy</code>; the Response section above lists any specific to this function. | |||
---- | ---- | ||
Back to [[TuCloudAPI]] | Back to [[TuCloudAPI]] | ||
[[Category:TuCloudAPI SuperRoot]][[Category:TuCloudAPI Operator]][[Category:TuCloudAPI Client]][[Category:TuCloudAPI]] | [[Category:TuCloudAPI SuperRoot]][[Category:TuCloudAPI Operator]][[Category:TuCloudAPI Client]][[Category:TuCloudAPI]] | ||
Latest revision as of 23:50, 3 November 2026
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
Edit a portal user in THIS PBX: name, active, priv_admin, role and phone are replaced as sent; disable_2fa=1 turns 2FA off and clears the secret (never enables). The password and the email are never changed here: a non-empty password is refused (field password, reason not_allowed); an email that is absent, empty, the confirmed address or the open one is ignored (a form re-posting the record never fails and never mails), a DIFFERENT one is refused (field email, reason not_allowed): the email changes with requestadminuseremail. A refusal writes nothing. tucloudpbx_id and root are NEVER changed. not_found if the login is not in this PBX. Requires a non-readonly ukey.
Call
https://tucloudapi.7kas.com:9087/tucloud?func=updateadminuser&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 and scopes every admin user to it. |
login |
string | Yes | — | The user's _id (login). A new user's is generated by the server and never shown. |
email |
string | No | — | Ignored when absent, empty, the current or the open address; any other value is refused. |
name |
string | No | — | Display name. |
active |
integer | No | 1 |
1 = active, 0 = disabled. |
priv_admin |
integer | No | 0 |
1 = super-admin flag. |
role |
string | No | — | Free-text role label. |
phone |
string | No | — | Phone. |
disable_2fa |
integer | No | 0 |
1 = disable 2FA and clear the secret (reset). |
Example
https://tucloudapi.7kas.com:9087/tucloud?func=updateadminuser&ukey=KEY&pbx=tucall&login=u0123456789abcdef&name=Ana&active=1
Response
{ok, user:{...}, status, email_pending, expires_in} | {ok:false, code, field?, reason?, message}.
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