Fiskil provides webhook delivery monitoring through the Console so you can track event delivery, troubleshoot failures, and ensure your integration remains reliable.

This guide outlines how to monitor webhook events and what logging practices you should implement on your side.

Webhook Monitoring in the Console

You can monitor webhook deliveries by visiting Console > Settings > Webhooks, then selecting a configured webhook endpoint.

For each registered webhook, the Console shows:

A list of recent events delivered to the endpoint
The delivery status (e.g. success or failure)
Response status code returned by your server
Timestamp of the event

This visibility helps identify integration issues such as:

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

How Fiskil Handles Failures

If Fiskil is unable to deliver a webhook (e.g. your server responds with an error or is unavailable), it will retry the event delivery up to 5 times, with increasing backoff intervals.

After the final attempt, the event is discarded. These attempts are all visible in the webhook log view for your endpoint.

See the Webhooks Guide for full delivery and retry details.

Recommended Logging on Your Side

To support observability, auditing, 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.

Related Guides

Was this page helpful?