Why no webhooks arrive after an abandoned flow
Webhooks only fire when a consent is established, so incomplete connection attempts are silent.
If a user starts the connection flow but doesn't complete it, you won't receive any webhook events. This is expected behaviour — this page explains why, and what to do when a user insists they did connect.
How the connection flow works
When your application initiates the connection flow, an auth session is created. The user must then complete the full consent authorisation process with their institution — their bank or energy provider — for a data-sharing consent to be established. Only once the consent is successfully created does Fiskil send a webhook event.
Why incomplete flows are silent
Webhooks are triggered by completed events — a consent being received, updated, or revoked, and data syncs that follow. If the user abandons the flow partway through, exits the institution's authorisation page, or hits an error at the institution, no consent is created, so there is nothing to notify you about.
Detecting abandonment
Because no webhook fires for an abandoned flow, don't rely on webhooks to detect drop-off. Track flow initiation in your own application, and treat the absence of a consent.received event within a reasonable window as an incomplete attempt. See the webhooks guide for the full event list.
If a user says they connected but you got no webhook
First rule out the common causes: the user may have abandoned the flow closer to the end than they realise, or hit an error on the institution's page. Also confirm your webhook endpoint is registered and reachable, and that you subscribed to consent events.
If it still looks like a genuine gap, contact Fiskil support with:
- The end user ID of the consumer who attempted to connect.
- The consent ID, if one was established.
- The date and time of the attempt.
- Screenshots of any errors the user saw.
Support can confirm whether a consent was actually created and whether webhook delivery was attempted.