Audit logs

Learn what audit logs are, what data they include, and how to use them in Voucherify

Audit logs give you a full history of activity in your Voucherify project. You can use them to track API requests, user actions, and system processes.

Data retention

Audit logs are stored for a limited time:

• Shared clusters: 6 months
• Dedicated clusters: 12 months

Audit logs overview

Tab	What it shows	Typical use
Logs	API requests and responses	Troubleshooting and debugging
Background Tasks	Asynchronous operations	Monitoring imports and system jobs
Exports	Exported data files	Downloading and reviewing data
Webhook Sendouts	Webhook deliveries	Tracking and retrying webhooks

Audit logs sections

In the Audit logs view, you can switch between several tabs:

• Logs – API requests and responses
• Background Tasks – asynchronous operations
• Exports – history of export files
• Webhook Sendouts – webhook delivery attempts

Each tab shows a different type of data.
Available columns and filters depend on the selected tab.

Logs show synchronous API requests. Background tasks show asynchronous operations processed in the background.

Logs

Use this tab to troubleshoot API requests, check errors, and inspect request and response data.

The Logs tab shows API interactions.

Each time a request is sent to Voucherify (via dashboard, API, or SDK), a log entry is created.

By default, logs display data from the last 24 hours. You can change the time range using filters.

What you can see

Each log includes:

• log ID
• date and time
• request source (channel)
• status (success or failure)
• API endpoint

Click a log ID to open detailed information about the request.

In log details, you can see:

• request and response data (JSON)
• who triggered the action (user or customer)
• related campaign or incentive
• request duration and result

Time formats

Logs display three time types:

• Project time – based on project settings
• Local time – based on your device
• Occurrence date (UTC) – used for sorting

Date filters use project time, but logs are ordered by UTC time.

Filters

In the Logs tab, you can filter data by:

• occurrence date
• channel
• status
• endpoint
• user
• server-side API key
• client-side API key

You can combine multiple filters to narrow results.

Background Tasks

Use this tab to monitor long-running operations such as imports or campaign updates.

The Background Tasks tab shows asynchronous operations such as:

• data imports
• campaign deletion
• export generation

Each task includes:

• status (scheduled, in progress, done, failed)
• processing status (success or failure)
• type of operation
• processing time and progress

Click a task ID to view detailed information about the operation.

You can filter background tasks by attributes such as type, status, and processing status.

Webhook Sendouts

Use this tab to track webhook delivery and retry failed sendouts.

The Webhook Sendouts tab shows all webhook delivery attempts.

For each webhook, you can see:

• sendout ID
• status
• request ID
• source ID
• creation and sendout dates

You can open detailed information about each sendout and retry failed deliveries.

Filters depend on sendout attributes such as status, type, or dates.

Exports

Use this tab to manage and download exported data files.

The Exports tab shows the history of generated export files.

For each export, you can see:

• status
• resource type
• export ID
• user who scheduled the export
• creation date

Click an export ID to view details such as applied filters and parameters.

You can filter exports by attributes such as resource and status.

Export logs

You can export logs based on filters applied in the Logs tab.

How it works:

1. Apply filters in the Logs tab
2. Select Export
3. Download the file when it is ready

• Exports are generated after a short delay
• Only filtered data is included in the export

Advanced filters (Enterprise)

You can filter logs by text in:

• request body
• response body

Browse exported logs

For API log exports, you can open the file directly in the dashboard.

The browser view lets you inspect exported log data without downloading the file.

• Click Browse data on a ready export
• The file opens in a browser view and may take a while to load
• The data is displayed based on selected columns
• Only exported fields are shown

Example:
If you export status, ID, and request body, only these fields are displayed.

Features

• search across the dataset (case-insensitive)
• you can further filter the data in the view
• original export filters are shown as read-only
• download the original CSV file at any time

For request and response bodies:

• a button opens a dialog with JSON content

Browsing is available only for:

• API log exports
• files ready for download
• files not older than 90 days

Import CSV logs

If a log is related to a CSV import, you can download the original file used in the import.

Example workflow

To investigate a failed request:

1. Go to the Logs tab
2. Filter by status = failure
3. Open a log ID
4. Review the request and response details