Event Notification API Specification - TPP Endpoints
Event Notification API Specification - TPP Endpoints
UK Open Banking Event Notifications API lets TPPs (third parties) subscribe to bank event streams — async notifications for account changes, consent revocations, customer status changes.
Replaces polling (saves API calls and network)
Not all banks fully implement (v3.1+ capability)
TPP registers webhook URL in bank portal → bank POSTs to URL on events → TPP validates signature and processes.
Uptime · 30-day window
About this API
Event Notifications API is Open Banking's mechanism for TPPs to use "event streams instead of polling". Background: early TPPs polling bank APIs periodically to know consent validity or account state changes (wasting quota and network). Event Notifications turns this into push — TPP registers webhook URL on bank portal, bank pushes immediately on relevant events (consent revocation, account freeze, customer data change). Critical for fintech app UX: after user clicks "revoke Klarna access" in bank app, Klarna knows in 1-5 seconds and stops access, instead of discovering 401 at next polling. Also satisfies compliance — TPPs must promptly respond to consent revocation; event mechanism makes this reliable.
What you can build
- 1User revokes consent in bank app — TPP receives real-time notification to stop access
- 2Fintech app immediately updates state when account is frozen
- 3Auto-sync customer data changes (address change, etc.)
- 4Compliance audit tracking consent lifecycle
Strengths & limitations
Strengths
- Replaces polling (saves API calls and network)
- Real-time (events arrive at TPP in 1-5 seconds)
- Standardized schema
Limitations
- Not all banks fully implement (v3.1+ capability)
- Webhook endpoint requires TPP to maintain availability
Getting started
TPP registers webhook URL in bank portal → bank POSTs to URL on events → TPP validates signature and processes.
FAQ
Can lost messages be replayed?+
Depends on bank implementation. Most support replay within a window.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST, Webhook
- SDKs
- python, javascript, go, java
- Response time
- 896 ms
- Last health check
- 6/26/2026, 6:23:58 AM
More from Openbanking Org Uk
UK Open Banking Account Information API (AIS) lets authenticated third parties read user bank account balance, transactions, and metadata with user consent.
UK Open Banking Confirmation of Funds API (CBPII) lets third parties query if a user account has sufficient funds — returns only yes/no, not the actual amount.
UK Open Banking API is the UK's statutory banking API standard — third parties access user account data and initiate payments with user consent (PSD2 compliance).
UK Open Banking Payment Initiation API (PIS) lets authenticated third parties initiate transfers from user bank accounts with user consent (A2A payments).