---
title: "List audit records"
method: GET
path: "/v1/audit"
tags: ["Audit"]
---

# List audit records

`GET /v1/audit`

## Request

- Base URL: `https://sandbox.pismolabs.io/audit-api`
- URL: `https://sandbox.pismolabs.io/audit-api/v1/audit`
- Auth: HTTP bearer

Returns paginated audit records based on filter parameters.

## Query parameters

- `page` integer
- `perPage` integer
- `order` 'asc' | 'desc'
- `beginDate` string, date-time
- `endDate` string, date-time
- `user` string
- `action` string
- `feature` string
- `featureID` string
- `cid` string

## Response `200`

OK

- SearchAuditPage
  - `current_page` integer: Current page number
  - `items` Audit[]
    - `http` AuditHttp, required: HTTP request and response details
      - `code` integer, required: HTTP status code returned by the operation
      - `request` string, required: Raw HTTP request payload
      - `response` string, required: Raw HTTP response payload
    - `id` integer, required: Identifier for the audit record
    - `operation` AuditOperation, required: Audit operation details
      - `action` string, required: Action performed in the system. These values vary based on the specific operation being audited, but common examples include: `create`, `update`, `delete`, `login`, and `logout`.
      - `audit_details` object, required: Additional audit context details
      - `changes` object, required: Map of field-level changes applied during the operation
      - `cid` string, required: Correlation ID for request tracing
      - `date` string, date-time, required: Datetime the operation was performed. Format = `yyyy-MM-ddTHH:mm:ssZ`
      - `description` object, required: Human-readable description of the operation
      - `feature` string, required: Feature area where the operation was performed. Values are specific to the service being audited, but common examples include: `user`, `card`, `transaction`.
      - `feature_id` string, required: Identifier of the resource within the feature
      - `feature_translation` object, required: Feature-specific translation details
      - `tenant` string, required: Tenant ID where the operation was performed
      - `origin` string: Origin identifier when the operation was triggered by another service. Common examples include: `console`, `api`, `scheduler`
      - `source_id` string: Source system identifier
    - `user` AuditUser, required: User details for the user who performed the action in the audit record
      - `email` string, required: Email of the user who performed the action
      - `id` string, required: ID of the user who performed the action
      - `roles` string[], required: List of roles assigned to the user who performed the action
    - `user_agent` AuditUserAgent, required: User agent details for the device from which the action in the audit record was performed
      - `device_ip` string, required: Device IP address
      - `user_agent_label` string, required: User-agent string from the device
    - `geographic_location` AuditGeographicLocation: Geographic location details
      - `latitude` number, double, required: Request origin's geographic latitude
      - `longitude` number, double, required: Request origin's geographic longitude
  - `pages` integer: Total number of pages
  - `per_page` integer: Number of items per page
  - `total_items` integer: Total number of items matching the query

## Other responses

- `400`: Bad Request
- `500`: Internal Server Error

---

[API](https://skmtc.dev/pismo/apis/control-center.md) - [All operations](https://skmtc.dev/pismo/apis/control-center/llms.txt) - [OpenAPI document](https://skmtc.dev/pismo/apis/control-center/revisions/3b41a64a5573?raw)