Capital.com API GET /api/v1/watchlists/{watchlistId}
The markets in one watchlist, each with its epic, name, status and current bid and offer.
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.
Read on Capital.com's own reference at open-api.capital.com on 12 Oct 2026: method, path, parameters and the example response. The reference does not flag the two session headers as required on each call. Its introduction says they should be passed on every request after login, which is why they are recorded as required.
Parameters
| Name | In | Type | Description |
|---|---|---|---|
| watchlistIdrequired | path | string | Watchlist identifier, from GET /api/v1/watchlists. |
Authentication headers
| Name | Type | Description |
|---|---|---|
| CSTrequired | string | Access token returned in the CST response header of POST /session. Valid for 10 minutes after last use. Placeholder only. |
| X-SECURITY-TOKENrequired | string | Account token returned in the X-SECURITY-TOKEN response header of POST /session. It selects the financial account. Placeholder only. |
Request
Written from the method, path and parameters recorded on this page, against the demo host. Not executed against a live or demo account. Credentials are read from environment variables on your own machine and are never entered on this site. The request builder writes these same snippets, from the same record.
Python
# Set CAPITAL_CST, CAPITAL_SECURITY_TOKEN as environment variables first. Never paste real values into code.
# CAPITAL_CST and CAPITAL_SECURITY_TOKEN hold the CST and X-SECURITY-TOKEN headers that POST /api/v1/session returns: step 3 of the quickstart (/brokers/capital-com/quickstart#step-3) captures them and this sample reads them back.
# Replace each {placeholder}, "..." and 0 with a real value before running.
import os
import requests
BASE_URL = "https://demo-api-capital.backend-capital.com" # the demo host
headers = {
"CST": os.environ["CAPITAL_CST"],
"X-SECURITY-TOKEN": os.environ["CAPITAL_SECURITY_TOKEN"],
}
resp = requests.get(BASE_URL + "/api/v1/watchlists/{watchlistId}", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())JavaScript
// Set CAPITAL_CST, CAPITAL_SECURITY_TOKEN as environment variables first. Never paste real values into code.
// CAPITAL_CST and CAPITAL_SECURITY_TOKEN hold the CST and X-SECURITY-TOKEN headers that POST /api/v1/session returns: step 3 of the quickstart (/brokers/capital-com/quickstart#step-3) captures them and this sample reads them back.
// Replace each {placeholder}, "..." and 0 with a real value before running.
// Run as a module, for example a .mjs file, on a Node version that has fetch built in.
const BASE_URL = "https://demo-api-capital.backend-capital.com"; // the demo host
const res = await fetch(BASE_URL + "/api/v1/watchlists/{watchlistId}", {
method: "GET",
headers: {
"CST": process.env.CAPITAL_CST,
"X-SECURITY-TOKEN": process.env.CAPITAL_SECURITY_TOKEN,
},
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());curl
# Set CAPITAL_CST, CAPITAL_SECURITY_TOKEN as environment variables first. Never paste real values into code.
# CAPITAL_CST and CAPITAL_SECURITY_TOKEN hold the CST and X-SECURITY-TOKEN headers that POST /api/v1/session returns: step 3 of the quickstart (/brokers/capital-com/quickstart#step-3) captures them and this sample reads them back.
# Replace each {placeholder}, "..." and 0 with a real value before running.
curl -X GET "https://demo-api-capital.backend-capital.com/api/v1/watchlists/{watchlistId}" \
-H "CST: $CAPITAL_CST" \
-H "X-SECURITY-TOKEN: $CAPITAL_SECURITY_TOKEN"Response
A mock response. The values are invented, so check field names against the official reference.
{
"_mock": true,
"markets": [
{
"epic": "MOCKMKT",
"instrumentName": "Mock market",
"symbol": "Mock",
"instrumentType": "COMMODITIES",
"marketStatus": "TRADEABLE",
"expiry": "-",
"lotSize": 1,
"bid": 22.041,
"offer": 22.061,
"high": 22.098,
"low": 21.926,
"netChange": -0.627,
"percentageChange": -0.27,
"updateTime": "2026-09-18T08:00:00.000",
"updateTimeUTC": "2026-09-18T08:00:00.000",
"delayTime": 0,
"streamingPricesAvailable": true,
"scalingFactor": 1
}
]
}Limits that apply at Capital.com
| Limit | Value | Scope | Source |
|---|---|---|---|
| Headline limit | 10/s per user | user | open-api.capital.comchecked |
Capital.com API errors you may meet
- error.account.limit.reachedHTTP 400. The demo account's balance cap has been reached, so it cannot be topped up further.
- error.invalid.accountHTTP 400. The account selected for a demo balance top up is not valid.
- error.invalid.accountIdHTTP 400. The account id sent when switching the active account is not valid.
- error.invalid.amountHTTP 400. The amount in a demo balance top up request is not valid.
- error.invalid.detailsHTTP 401. Invalid credentials on session creation.
- error.invalid.fromHTTP 400. The from parameter of an activity history request is not valid.
All Capital.com API error codes, including 18 more not listed here.