# Capital.com OHLCMarketData.unsubscribe Independent and unofficial. Not affiliated with or endorsed by any broker or platform named here. Educational only: nothing here is advice, and nothing here recommends a broker or a trade. This is the markdown version of https://openbrokerapi.com/brokers/capital-com/messages/ohlcmarketdata-unsubscribe, written from the same records as that page. Risk warning: CFDs and spread bets are complex instruments and come with a high risk of losing money rapidly due to leverage. You can lose money on these products, and each provider publishes its own loss figure under FCA rules. You should consider whether you understand how they work and whether you can afford to take the high risk of losing your money. Automated and API trading can amplify losses through bugs, connectivity failures and runaway orders. Stops candlestick bar updates. You unsubscribe from what you name: an epic alone stops every resolution and bar type for that epic. - Message: `OHLCMarketData.unsubscribe` - Interface: Capital.com WebSocket API - Group: Live candles - Status: verified. Source: [open-api.capital.com](https://open-api.capital.com/#section/WebSocket-API/Unsubscribe-from-OHLC-market-data), checked 2026-10-12. This is a message of the Capital.com WebSocket API, not an HTTP endpoint. It has no method and no path: it is sent as JSON over an open WebSocket connection. It is in no OpenAPI file on this site and the request builder does not list it. ## The message - Name: `OHLCMarketData.unsubscribe` - Direction: Request, sent by the client - Carried by: WebSocket. Capital.com's page says to ping the service at least once every 10 minutes to keep the connection alive. - WebSocket address: `wss://api-streaming-capital.backend-capital.com/connect` ## Fields - `destination` (type not stated, required or not: not stated): Names the message, in the way a path names a REST call. Here it is OHLCMarketData.unsubscribe. - `correlationId` (type not stated, required or not: not stated): An id of your own. The answer carries the same value, which is how an answer is matched to its request. - `cst` (type not stated, required or not: not stated): The token that identifies the client. It is the CST value returned when a session is started over REST. - `securityToken` (type not stated, required or not: not stated): The token that identifies the account in use. It is the X-SECURITY-TOKEN value returned when a session is started over REST. - `payload.epics` (type string[], required): The epics to stop. - `payload.resolutions` (type string[], optional): The bar widths to stop: MINUTE, MINUTE_5, MINUTE_15, MINUTE_30, HOUR, HOUR_4, DAY or WEEK. Left out, every resolution is stopped. - `payload.types` (type string[], optional): The kinds of candlestick to stop: classic or heikin-ashi. Left out, every kind is stopped. Note that the field is types here and type on the subscribe message. ## What arrives `OHLCMarketData.unsubscribe`: The confirmation that the updates were stopped. - `status` (type not stated, required or not: not stated): OK in the vendor's example of a successful answer. - `destination` (type not stated, required or not: not stated): The destination of the request it answers: OHLCMarketData.unsubscribe. - `correlationId` (type not stated, required or not: not stated): The correlationId the request carried. - `payload.subscriptions` (type not stated, required or not: not stated): An object with one entry for each combination stopped, keyed as epic, resolution and type joined by colons. In the vendor's example the value is PROCESSED. ## Sample Written by this site from the fields recorded on this page. It has not been run against a terminal, a server or an account, and the values in it are placeholders. No credential is typed into it: where a field holds one, the placeholder says where it comes from. Nothing is entered on this site. ```json { "destination": "OHLCMarketData.unsubscribe", "correlationId": "4", "cst": "", "securityToken": "", "payload": { "epics": [ "OIL_CRUDE" ], "resolutions": [ "MINUTE", "MINUTE_5" ], "types": [ "heikin-ashi" ] } } ``` ## Limits that apply at Capital.com - Headline limit: 10/s per user - Scope: user - Status: verified. Source: [open-api.capital.com](https://open-api.capital.com/), checked 2026-09-18. - Note: Orders and new positions: 1 per 0.1 s. POST /session: 1 a second per API key. Demo: 1000 an hour for POST /positions and /workingorders. ## Related Capital.com messages: Live candles - [ohlc.event](https://openbrokerapi.com/brokers/capital-com/messages/ohlc-event): Carries one candlestick bar update for an epic subscribed to with OHLCMarketData.subscribe: the open, high, low and close for one resolution and bar type. - [OHLCMarketData.subscribe](https://openbrokerapi.com/brokers/capital-com/messages/ohlcmarketdata-subscribe): Subscribes to candlestick bar updates for a list of epics, at chosen resolutions and for a chosen bar type. An answer confirms each combination, then an ohlc.event message arrives for each update. ## More on Capital.com - [All Capital.com messages](https://openbrokerapi.com/brokers/capital-com/messages): 7 documented here, grouped by what they do. - [Capital.com API quickstart](https://openbrokerapi.com/brokers/capital-com/quickstart) - [All Capital.com error codes](https://openbrokerapi.com/errors/capital-com) - [Capital.com API page](https://openbrokerapi.com/brokers/capital-com): The full record: access, authentication, limits and the source for each. ## Licence and how to cite The records behind this page are all rights reserved. This file is the page itself, at its own address, in another format. It is not part of the CC BY 4.0 downloads listed at https://openbrokerapi.com/data. Quote from it with a link to the page. Cite as: Capital.com OHLCMarketData.unsubscribe. Broker API Hub, https://openbrokerapi.com/brokers/capital-com/messages/ohlcmarketdata-unsubscribe, newest check 2026-10-12. Where you rely on a single figure, cite the source and the checked date printed beside it as well. Where this page and a broker's own documentation differ, the documentation wins.