Skip to content

User audit log

API path: /user/audit/log.

audit_object type is JSON object:

    "id": 1, // ID of the audit record
    "user_id": 3, // Master user's ID
    "subuser_id": 3, // ID of the subuser who made an action
    "entry_category": "user", // Category of the entry on which an action was made
    "entry_id": null, // Nullable. ID of the entry on which an action was made
    "action": "login", // Action on entry
    "payload": null, // Nullable json-object. Additional information about action 
    "host": "", // Host from which an action was made. IPv4 or IPv6
    "user_agent": "Apache-HttpClient/4.1.1 (java 1.5)", // User agent
    "action_date": "2018-09-03 11:32:34" // Date and time of the action


Gets list of audit records available for current user.

required subuser rights: admin (available only to master users)


  • fromstring. Include audit objects recorded after this date, e.g. 2014-07-01 00:00:00.
  • tostring. Include audits before this date, e.g. 2014-07-01 00:00:00.
  • subuser_idsint[]. (optional) Include audits for specific subusers, e.g. [2, 3].
  • actionsstring[]. (optional) Include audits for specific actions only, e.g. ["user_checkin"]. Set of valid values is formed by combinations of entry categories and actions.
  • limitint. Pagination. Maximum number of audit records to return, e.g. 10.
  • offsetint. Pagination. Get audits starting from, e.g. 0.
  • sortstring[]. (optional) Set of sort options. Each option is a pair of property name and sorting direction, e.g. ["action_date=acs", "user=desc"]. Properties available for sorting by:
    action_date (sort only by date, not considering time part)
    action_datetime (sort by date including time)
    user (sort by user's (subuser) last+first+middle name, not by ID)
    If no sort param is specified, then sorting equivalent to option ["action_date=asc"] will be applied.


    "success": true,
    "list": [ <audit_object>, ... ]

Last update: August 21, 2020