The webhook delivery channel. Upvest sends HTTPS POST requests to your registered endpoint containing one or more events. Events within a single request are ordered by created_at in ascending order. There are no ordering guarantees across separate requests.
Events related to user lifecycle changes including creation, updates, and status transitions.
Content-Type: application/json
UserCheckEvent
Events related to user compliance and verification check outcomes.
Content-Type: application/json
AccountEvent
Events related to investment account lifecycle changes including opening, closing, and status updates.
Content-Type: application/json
AccountGroupEvent
Events related to account group changes.
Content-Type: application/json
OrderEvent
Events related to the order lifecycle including placement, processing, filling, and rejection. Every order status change emits a webhook event.
Content-Type: application/json
OrderCancellationEvent
Events related to order cancellation requests and their outcomes.
Content-Type: application/json
ExecutionEvent
Events related to order execution fills. Every execution associated with an order has its own set of statuses, and every status change emits a webhook event.
Content-Type: application/json
PositionEvent
Events related to changes in holdings and positions within accounts.
Content-Type: application/json
CashBalanceEvent
Events related to changes in account cash balances.
Content-Type: application/json
PortfolioEvent
Events related to portfolio creation, updates, and allocation changes.
Content-Type: application/json
RebalancingEvent
Events related to portfolio rebalancing execution and completion.
Content-Type: application/json
SavingsPlanEvent
Events related to savings plan creation, execution, and status changes.
Content-Type: application/json
DirectDebitEvent
Events related to direct debit funding operations and their status transitions.
Content-Type: application/json
WithdrawalEvent
Events related to cash withdrawal processing and completion.
Content-Type: application/json
MandateEvent
Events related to direct debit mandate creation and revocation.
Content-Type: application/json
SecuritiesTransferEvent
Events related to inbound and outbound securities transfer operations.
Content-Type: application/json
AccountTransferEvent
Events related to account transfer operations between entities.
Content-Type: application/json
CorporateActionEvent
Events related to corporate actions on held securities such as dividends, splits, and mergers.
Content-Type: application/json
LiquidationEvent
Events related to account liquidation operations.
Content-Type: application/json
ReportEvent
Events related to report generation completion.
Content-Type: application/json
FeeEvent
Events related to fee charges on accounts.
Content-Type: application/json
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.