Single WebSocket channel for all destinations. Clients send frames whose `destination`
field selects an operation (marketData.subscribe, marketData.unsubscribe,
OHLCMarketData.subscribe, OHLCMarketData.unsubscribe, ping). The server publishes
subscription confirmations, market data updates, OHLC bar updates, and ping responses
on the same connection.
Provider:Capital.com Public APIAsyncAPI: v2.6.0Spec: Capital.com WebSocket Streaming APIOperations: 2Messages: 9
Channel address
/
Operations
publish
sendClientFrame
Frames sent from the client to Capital.com.
subscribe
receiveServerFrame
Frames received from Capital.com.
Messages
marketDataSubscribe
Subscribe to live bid/offer price updates for a set of instrument epics.
Content-Type:
marketDataUnsubscribe
Remove real-time price subscriptions for one or more epics.
Content-Type:
ohlcMarketDataSubscribe
Subscribe to OHLC candle updates for a set of epics, resolutions, and bar type.
Content-Type:
ohlcMarketDataUnsubscribe
Remove OHLC subscriptions for the given epics, with optional resolution and type filters.
Content-Type:
ping
Keep the WebSocket session alive (must be sent at least every 10 minutes).
Content-Type:
subscriptionStatus
Confirms processing status of a subscribe or unsubscribe request per epic.
Content-Type:
marketDataUpdate
Streaming bid/offer quote update for a subscribed instrument.
Content-Type:
ohlcMarketDataUpdate
Streaming OHLC bar update for a subscribed instrument and resolution.
Content-Type:
pingResponse
Server acknowledgement of a client 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.