Checking connection status and logs in the console

The Fiskil Console is your first stop when something doesn't look right — before you write to support, you can usually see for yourself whether a request was made, a consent exists, or a webhook was delivered.

End users and consents

The End-Users page in the console lists the end users on your team. From an end user you can create auth sessions and follow their connection activity — useful when a user reports that they "definitely connected" and you want to confirm whether a consent was actually established. For how consent states work, see Consent lifecycle and renewal.

Request logs

Request logs record the API calls made to Fiskil with your API keys, and are retained for 90 days under the Logs tab. For each request you can see:

1. Endpoint and method (e.g. GET /banking/accounts).
2. Team ID and end user ID (where provided).
3. Timestamp, HTTP status code, and latency.
4. Source IP address, user agent, and response size.

You can filter by date range, end user ID, and path — so "did my server actually call the transactions endpoint for this user yesterday, and what status did it get?" is answerable in a few clicks.

Webhook logs

Webhook delivery logs are also retained for 90 days. Under Settings, open a registered webhook to see its recent events, whether each delivery succeeded or failed, the HTTP status code your server returned, and when the attempt was made. If events seem to be missing, start with Why aren't my webhooks arriving?

Audit logs

Audit logs capture changes made in the console itself — API keys created or deleted, webhooks added or removed, team membership changes, and so on. They're available to users with the owner role. See the Monitoring & Logs guide for the full list of logged events.

What to capture before contacting support

If the logs don't explain the issue, gather these before raising a ticket — they let support trace the exact request or delivery:

1. Your team ID.
2. The end user ID and consent ID involved.
3. The timestamp (with timezone) of the request or expected event.
4. The endpoint or event name, and the HTTP status you saw.
5. The error id from any API error response.