Skip to content

Get logs

GetLogs

GetLogs

Description: Returns server audit log records from the new TSV-based journal. Results are sorted from newest to oldest.

Access Control

🛡️ Access Level Required: SESSION_ADMIN, SESSION_MANAGER, or SESSION_DEALER


Request Parameters

Name Type Required Description
from int Yes Start of time range as Unix timestamp
to int Yes End of time range as Unix timestamp
limit int Yes Maximum number of rows to return
offset int Yes Row offset inside filtered result set
actor_type string No Exact filter by actor type: CLIENT, MANAGER, or SYSTEM
actor_id string No Exact filter by actor identifier
action string No Exact filter by action name
status string No Exact filter by status: SUCCESS, ERROR, WARNING, INFO
source string No Exact filter by source
detail string No Partial match inside detail field
filter string No Global text search across the whole log record

Response Structure

The response returns rows with the following structure:

Field Type Description
time string UTC timestamp in YYYY-MM-DDTHH:MM:SSZ format
actor_type string Actor category
actor_id string Actor identifier or -
action string Operation name
status string Operation status
source string Request origin, IP, plugin name, or module name
detail string Free-form payload or message

Request Example

{
  "from": 1713744000,
  "to": 1713830399,
  "limit": 100,
  "offset": 0,
  "actor_type": "MANAGER",
  "status": "INFO",
  "action": "AuthManager",
  "filter": "127.0.0.1"
}

Response Example

{
  "structure": [
    "time",
    "actor_type",
    "actor_id",
    "action",
    "status",
    "source",
    "detail"
  ],
  "rows": [
    [
      "2026-04-22T12:00:00Z",
      "MANAGER",
      "1223",
      "AuthManager",
      "INFO",
      "127.0.0.1",
      "POST /auth/manager"
    ]
  ],
  "count": 1
}

Notes

  • Log storage format is internal TSV, but API responses are returned as structured fields.
  • offset and limit are applied after filtering.
  • count is the total number of filtered rows before pagination.