v20251007_k – Added

Audit log

This version brings new filters and functionalities to Logs. Thanks to these changes, you can quickly find relevant logs for analytics or troubleshooting.

New filters

Users with the Read events and technical logs permission can now find data quicker in the Audit logs thanks to the new filters:

• Endpoint: Lists all logs for a specific endpoint, for example POST_v1_vouchers_import_csv.
• User: Lists all logs for actions performed by a given organization user. It requires Access to Project's Users list permission.
• Server-side API key: Lists all logs performed with a given server-side API key. The filter uses the key name, so the key itself is protected. It requires Access Project Settings permission.
• Client-side API key: Lists all logs performed with a given client-side API key. The filter uses the key name, so the key itself is protected. It requires Access Project Settings permission.

Export API logs – API endpoint

You can also export API logs in a CSV file with the POST /v1/exports – Create exports endpoint. Pass "exported_object": "api_log" in the request body. You can use the following parameters:

• fields: "id", "created_at", "status", "request_id", "channel", "method", "endpoint", "url", "user_email", "app_id", "client_app_id", "request_duration", "request_body", "response_body".
• filters: created_at (with $before and $after conditions), status (with $is and $is_not conditions), channel (with $in, $not_in conditions), app_id and client_app_id (both with $in, $not_in, $is, and $is_not conditions).
• order: created_at (ascending order), -created_at (descending order).