TuCloudAPI updatetask: Difference between revisions

Latest revision as of 14:31, 3 August 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 your ukey owns that PBX; otherwise it returns {"ok":false,"code":"forbidden"}.

Description

Edit a task (does not change status). 404 if not in the caller's PBX.

Call

GET  https://tucloudapi.7kas.com:9087/tucloud?func=updatetask&ukey=YOUR_KEY&pbx=PBX_NAME

Requires the ukey parameter. Always HTTP 200; 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	—	Task id (_id).
`name`	string	Yes	—	Task name (required).
`description`	string	No	—	Optional description.
`time`	string	No	`00:00`	Time of day HH:MM.
`second`	integer	No	`0`	Second 0-59.
`month`	integer	No	`0`	Month 1-12; 0 = any.
`dayofmonth`	integer	No	`0`	Day of month 1-31; 0 = any.
`dayofweek`	integer	No	`0`	Day of week 0-6; 7 = any.
`hold`	integer	No	`0`	1 = recurring, 0 = one-shot.

Example

https://tucloudapi.7kas.com:9087/tucloud?func=updatetask&ukey=KEY&pbx=tucall&id=224&name=Verano

Response

{ok, task:TASK}.

Errors

Always HTTP 200. On failure the body is {"ok":false,"code":"...","message":"..."}. Codes: missing_pbx, unknown_pbx, forbidden, invalid_param, not_found, db_error, server_busy.

Back to TuCloudAPI

@@ Line 14: / Line 14: @@
 ! Parameter !! Type !! Required !! Default !! Meaning
 |-
-| <code>pbx</code> || string || Yes || — || TuCloud PBX NAME (e.g. tucall). The (ukey, pbx) pair is the tenant boundary; the server verifies the ukey owns this PBX.
+| <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.
 |-
 | <code>id</code> || integer || Yes || — || Task id (_id).