Jump to content

TuCloudAPI getpbxloclog

From Wiki 7Kas

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

Description

FuturePBX IVR/locution DTMF key-press log for a period. Role-resolved (clients see only their own account; operators their scope; SuperRoot all). Single SQL function; unset filters default to NULL server-side.

Call

https://tucloudapi.7kas.com:9087/tucloud?func=getpbxloclog&ukey=YOUR_KEY

GET, or POST with the parameters form-urlencoded in the body. Requires the ukey parameter.

Parameters

Parameter Type Required Default Meaning
year integer Yes — Year (e.g. 2026).
month integer Yes — Month, 1-12.
day integer No — Filter by day of month (1-31).
hour integer No — Filter by hour (0-23). (only valid together with day)
accountcodeid integer No — Filter by account id (non-clients). Forced to own for clients.
tucloudpbx_id integer No — Filter by virtual PBX id.
loc_id integer No — Filter by locution/IVR id.
pbxname string No — Filter by PBX name. (max length 32)
pressed string No — Filter by DTMF key(s) pressed. (max length 80)
src string No — Filter by source number. (max length 80)
dst string No — Filter by destination number. (max length 80)
limit integer No 100 Max rows (PostgreSQL up to 1000).
offset integer No 0 Pagination offset.

Example

https://api.7kas.com:9087/tucloud?func=getpbxloclog&ukey=KEY&year=2026&month=7&limit=100

Response

FillRecords2JSON records.


Back to TuCloudAPI