Fills feed channel. Clients send command frames (getMarkets, subscribe, unsubscribe) and receive market lists, subscription acks, fill events, and (optionally) head updates for Mango V4 Perp and Openbook markets.
Receive fill events and control responses from the Fills Feed
Messages
getMarkets
Request the list of markets the server currently supports.
Content-Type:
fillsSubscribe
Subscribe to fill events. Per the service-mango-fills README a client can subscribe by marketIds or by Mango account. The TypeScript client additionally documents marketId, accountIds, and a headUpdat
Content-Type:
fillsUnsubscribe
Unsubscribe from fill events for a given marketId.
Content-Type:
marketsList
Map of market pubkey -> market name returned in response to getMarkets.
Content-Type:
subscriptionAck
Server acknowledgement of a subscribe/unsubscribe command.
Content-Type:
fillEventUpdate
Individual fill event for a Mango V4 Perp or Openbook market. status is 'new' for confirmed fills and 'revoke' when a fill that previously occurred on a fork is rolled back.
Content-Type:
headUpdate
Event-queue head pointer update, emitted when the client subscribed with headUpdates=true.
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.