1. Audit Interface
The Audit interface is designed to help clients efficiently search, filter, and analyze system-generated logs related to their organization. Audit The layout includes:- Filters panel
- Paginated audit log list
- Log detail view access
2. Using the Audit Module
The Audit section enables clients to review platform activity at both summary and detailed levels.Filtering Audit Records
The Filters panel allows clients to narrow down audit logs using multiple parameters: Client — Displays the logged-in client name Log Source — Filter logs based on origin (e.g., SDK Audit, SearchEngine Audit) Session ID — Locate logs related to a specific session for complete traceability Date Range (From / To) — Define a custom time window for retrieving logs Items per Page — Control how many audit records are displayed per page A Clear Filters option resets all applied filters to default values. Audit FiltersReviewing Audit Logs
Audit records are displayed in a structured list format for easy review. Each entry includes: Session ID — Unique identifier linking related activities API — The API endpoint or system function triggered Message — Description of the event (e.g., login successful) Status — Outcome of the action (e.g., Success) Response Code — HTTP or system response code (e.g., 200) Timestamp — Exact date and time the event occurred Audit LogsViewing Log Details
Each audit record includes a View option. Clicking View provides expanded details about the selected log entry. The detailed view may include:- Complete event information
- API execution details
- Response metadata
- Error information (if applicable)
- Session-level trace data
- Issue investigation
- API troubleshooting
- Compliance validation
- Operational analysis
3. Operational Use Cases
The Client Audit module is commonly used for:- Monitoring user login activity
- Investigating failed API calls
- Tracing session-based actions
- Reviewing system events for compliance
- Debugging integration issues
- Validating transaction-related activity