Jump to content

TuCloudAPI getextension

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

Get one extension with all editable fields (NO password). mode is REGISTRO (registered SIP) or TOEXT (sends to another extension). 404-style {ok:false,not_found} if not in the caller's PBX.

Call

https://tucloudapi.7kas.com:9087/tucloud?func=getextension&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 — Extension id (_id).

Example

https://tucloudapi.7kas.com:9087/tucloud?func=getextension&ukey=KEY&pbx=tucall&id=87365

Response

{ok, ext:{_id,num,name,ringtime,internalcli_id,teamsopt,teamsnum,peerid,pickupgroup,toext_id,is_trunk,mode,user,backupnum,backupmonpeer,music,tom,voicemail,email,incom_only_contacts,fwdshowcaller,fwd_cli,fwd,fwdnum,fwd_internal,fwdnum_internal,cli_id,recoutgoing,only_contacts,outs_id,nota,hash_presence}}. hash_presence is the presence key (see getextensions); the account hash16 it derives from is NEVER exposed.

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