Jump to content

TuCloudAPI updatephonebook

From Wiki 7Kas

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 phonebook. 404 if not in the caller's PBX. Requires a non-readonly ukey.

Call

https://tucloudapi.7kas.com:9087/tucloud?func=updatephonebook&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 — Phonebook id (_id).
name string Yes — Phonebook name (required, unique per tenant, max 128).
description string No — Optional description (max 256).
color string No #3b82f6 Hex color #RRGGBB.
icon string No bi-journal-bookmark Bootstrap-icons name (max 32).
is_personal integer No 0 1 = personal, 0 = shared.

Example

https://tucloudapi.7kas.com:9087/tucloud?func=updatephonebook&ukey=KEY&pbx=tucall&id=1&name=Comercial

Response

{ok, phonebook:{...}}.

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