Up · AsyncAPI Specification
Up Personal Banking Webhooks
Version v1
Event surface for the Up Personal Banking API. Once a webhook is registered (POST /webhooks), Up delivers JSON-encoded POST callbacks to the configured URL whenever transaction activity occurs on the account. Every callback carries an X-Up-Authenticity-Signature header, which is the HMAC-SHA256 of the raw request body signed with the per-webhook secretKey returned at creation time. The subscriber URL must respond 200 within 30s or delivery is retried with exponential backoff. Derived verbatim from the webhook callback definition in Up's published OpenAPI 3.0.3 contract.
View Spec
View on GitHub
FinancialBanksOpen BankingCDRConsumer BankingAustraliaNeobankProduct Reference DataAsyncAPIWebhooksEvents
Channels
webhook-events
Receive Up webhook events
The subscriber-hosted URL registered via POST /webhooks. Up POSTs webhook-event callbacks here.
Messages
TransactionCreated
Transaction created
A new transaction was created on the account.
TransactionSettled
Transaction settled
A transaction transitioned from HELD to SETTLED.
TransactionDeleted
Transaction deleted
A HELD transaction was deleted (e.g. a hotel pre-auth released).
Ping
Ping
Manually triggered test event via POST /webhooks/{webhookId}/ping.