AsyncAPI channel · Mercury · Mercury Webhooks

/mercury/webhook

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.

Open source AsyncAPI → All Mercury channels Mercury provider profile
Provider: Mercury AsyncAPI: v2.6.0 Spec: Mercury Webhooks Operations: 1 Messages: 7

Channel address

/mercury/webhook

Operations

publish
receiveMercuryWebhook
Receive a Mercury webhook event

Messages

TransactionCreatedEvent
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.

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