Consents & connections
How consents work on Fiskil, the consent lifecycle, and how to manage renewals, revocations, and duplicates.
A consent is an end user's authorisation for your application to access their data at an institution — a bank, energy retailer, or other data holder. Every connection your users make through Fiskil is backed by a consent, and that consent controls what data you can access and for how long.
The lifecycle at a glance
- Created — an end user completes the consent flow and authorises your app at their institution.
- Active — Fiskil syncs data for the consent and delivers it via the Data API and webhooks.
- Expiring — every consent has an expiry date. Before it's reached, your app can ask the user to renew.
- Renewed, expired, or revoked — a renewed consent continues with a new expiry. Otherwise the consent ends: data syncing stops, and in Australia (CDR) you're required to delete the data associated with it.
In this section
- Consent lifecycle and renewal — what triggers renewal events and how to handle them.
- Revoke a consent via the API — end data sharing for a single connection.
- Duplicate consents — identify and remove accidental duplicates.
- Multiple active consents — what happens when one user holds several consents for the same institution.
For endpoint schemas and integration guides, see the developer documentation.