Single subscriber endpoint that receives every Mercury webhook event the
registration is subscribed to. The event class is identified by the
combination of `resourceType` and `operationType` on the JSON body.
Mercury sends one event per HTTP POST.
A new transaction was created on a Mercury account.
Content-Type: application/json
TransactionUpdatedEvent
An existing transaction was modified on a Mercury account.
Content-Type: application/json
CheckingAccountBalanceUpdatedEvent
The balance on a Mercury checking account changed.
Content-Type: application/json
SavingsAccountBalanceUpdatedEvent
The balance on a Mercury savings account changed.
Content-Type: application/json
TreasuryAccountBalanceUpdatedEvent
The balance on a Mercury Treasury account changed.
Content-Type: application/json
CreditAccountBalanceUpdatedEvent
The balance on a Mercury credit account changed.
Content-Type: application/json
InvestmentAccountBalanceUpdatedEvent
The balance on a Mercury investment account changed.
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.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.