AsyncAPI channel · Up · Up Personal Banking Webhooks

webhook-events

The subscriber-hosted URL registered via POST /webhooks. Up POSTs webhook-event callbacks here.

Open source AsyncAPI → All Up channels Up provider profile
Provider: Up AsyncAPI: v2.6.0 Spec: Up Personal Banking Webhooks Operations: 1 Messages: 4

Channel address

webhook-events

Operations

receiveWebhookEvent
Receive Up webhook events

Messages

TRANSACTION_CREATED
A new transaction was created on the account.
Content-Type:
TRANSACTION_SETTLED
A transaction transitioned from HELD to SETTLED.
Content-Type:
TRANSACTION_DELETED
A HELD transaction was deleted (e.g. a hotel pre-auth released).
Content-Type:
PING
Manually triggered test event via POST /webhooks/{webhookId}/ping.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.