Events

Events mark changes or behaviour in entities and can be used to trigger actions in your application.

Entities and their events

EntityEvent TypeDescriptionWebhook Available
Connectionconnection.createdWhen a connection is created
Connectionconnection.updatedWhen a connection is updated
Connectionconnection.deletedWhen a connection is deleted
Connectionconnection.invalidatedWhen a connection status changes from active to invalid due to user-related errors. The specific user-related errors that should trigger this event for web and OB connections are as follows:
Web Connections: user-action-required, invalid-username-or-password, invalid-connection, locked-account, multifactor-required
OB Connections: expired CDR arrangement - user didn’t re-authorize, any issue occurred during user re-authorization
Connectionconnection.activatedwhen a connection is activated
Accountaccount.updatedWhen an account is updated or a change is made to existing account attributes
Transactionstransactions.updatedWhen a new transaction is added for a user through various scenarios: creating a new connection (web, Open Banking, or CSV/PDF) whether or not previous transactions exist, updating an existing connection, or refreshing a connection manually, via a scheduler
Consentconsent.createdWhen a consent is created
Consentconsent.expiredWhen a consent is expired
Consentconsent.reminderWhen a consent has been active for 90 days since the last update
Consentconsent.revokedWhen a consent is revoked
Consentconsent.updatedWhen a consent is updated
Consentconsent.warningWhen a consent is about to expire
Useruser.createdWhen a user is created
Useruser.deletedWhen a user is deleted
Useruser.updatedWhen a user is updated

📘

Consent events

Any events around consent must be monitored if your application is using Open Banking data. For more information please read our documentation on data governance events.