Monitoring & Logs

The Fiskil platform gives you clear visibility into activity across your account and API usage. Logs help you track changes, investigate issues, and maintain security and compliance. Fiskil provides multiple log types, audit logs for console actions, request logs for incoming API traffic, and webhook logs for outgoing API traffic, offering a complete view of your platform's operations.

Log Types

Fiskil provides multiple categories of logs to help you monitor activity, troubleshoot issues, and maintain visibility into your platform usage:

All logs can be viewed in the Fiskil Console. Exporting or log draining is not currently supported.

Audit Logs

Audit logs can be viewed in the Fiskil Console under Settings > Data API > Audit Logs. It is only available to team users with owner role. The following table lists the currently logged audit events, their categories, and descriptions.

Request Logs

Request logs record incoming API requests made to the Fiskil platform using your API keys. They are retained for 90 days and can be viewed in the Fiskil Console under the Logs tab.

For each request, the Console displays:

• Endpoint & Method -- e.g., GET /banking/accounts.
• Team ID and End User ID (if provided).
• Timestamp -- When the request was received.
• Status Code -- The HTTP status code returned.
• IP Address -- Source of the request.
• User Agent -- The client making the request.
• Response Size and Latency.

Logs can be filtered by date range, end_user_id and path. These logs help you debug requests, analyze API performance, and monitor traffic patterns.

Webhook Logs

Webhook logs record outgoing webhook deliveries from the Fiskil platform to your configured endpoints. They are retained for 90 days and can be viewed in the Fiskil Console by navigating to Settings > Webhooks and selecting a registered webhook.

For each webhook endpoint, the Console displays:

• Recent Events -- A list of events delivered to the endpoint.
• Delivery Status -- Whether the delivery was successful or failed.
• Response Status Code -- The HTTP status code returned by your server.
• Timestamp -- When the delivery attempt was made.

This visibility helps you quickly identify and resolve integration issues, such as:

• Unreachable or misconfigured endpoints.
• Unexpected 4xx or 5xx responses.
• Delivery retries due to timeouts or failures.

Recommended Logging on Your Side

To better support observability, and troubleshooting within your own application, we recommend logging the following:

• All incoming webhook payloads (excluding sensitive fields)
• Response status codes your server returns
• Any webhook verification failures (e.g. invalid signature)
• Internal processing outcomes (e.g. sync success, validation errors)

Your logs should include:

• message_id from the webhook payload (for deduplication and tracing)
• event name (e.g. transactions.sync.completed)
• Timestamps for when your system processed each event

These logs will be essential when debugging failed syncs or investigating data availability issues.

Recommendations for Monitoring

To get the most value from Fiskil's monitoring and logging capabilities, we recommend the following best practices:

• Regularly review audit logs to track account changes and ensure compliance with organizational policies.
• Monitor request logs to detect performance bottlenecks, unusual traffic patterns, or failed API calls that may indicate issues or misuse.
• Check webhook logs frequently to verify successful deliveries and promptly resolve integration problems.
• Secure access to logs by restricting viewing permissions to authorized team members, maintaining data privacy and integrity.

Following these practices helps maintain operational visibility, detect issues early, and support security and compliance efforts effectively.

Related Guides

• Webhooks Guide
• Security
• Support & Troubleshooting