TradeLocker API GET /trade/sessions/{sessionId}

GET/trade/sessions/{sessionId}Instruments and Sessions

Read one trade session: its time zone, its opening periods, its holidays and whether trading is blocked.

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.

Independent and unofficialpublic-api.tradelocker.comchecked 12 Oct 2026

Read on 12 Oct 2026 on TradeLocker's own reference page for this call, in the Markdown version the documentation site serves at the same address with .md on the end. That page carries the call's OpenAPI definition, headed Trading API version 2.11.0: the method, path, parameters and required marks here are that definition's. The reply object d marks blockTrading and timeZone as required and also lists holidays and five period objects: session_preopen, session_beforemarket, session_regular, session_aftermarket and session_postclose. No mock reply is recorded.

Parameters

Name	In	Type	Description
sessionIdrequired	path	integer	The identifier of the trade session, the tradeSessionId in an instrument's details.
accNumrequired	header	integer	The account number that selects which of the login's accounts the call acts on. It is the accNum from GET /auth/jwt/all-accounts, not the accountId.

Authentication headers

Name	Type	Description
Authorizationrequired	string	Send Bearer followed by the accessToken from POST /auth/jwt/token. The reference marks the call as secured by a bearer JWT. Placeholder only: never paste a real token into this site.

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 TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
# TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
# Replace each {placeholder}, "..." and 0 with a real value before running.
import os
import requests

BASE_URL = "https://demo.tradelocker.com/backend-api"  # the demo host
headers = {
    "Authorization": "Bearer " + os.environ["TRADELOCKER_ACCESS_TOKEN"],
    "accNum": os.environ["TRADELOCKER_ACC_NUM"],
}
resp = requests.get(BASE_URL + "/trade/sessions/{sessionId}", headers=headers, timeout=10)
resp.raise_for_status()
print(resp.json())

JavaScript

// Set TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
// TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
// 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.tradelocker.com/backend-api"; // the demo host
const res = await fetch(BASE_URL + "/trade/sessions/{sessionId}", {
  method: "GET",
  headers: {
    "Authorization": "Bearer " + process.env.TRADELOCKER_ACCESS_TOKEN,
    "accNum": process.env.TRADELOCKER_ACC_NUM,
  },
});
if (!res.ok) throw new Error(`HTTP ${res.status}`);
console.log(await res.json());

curl

# Set TRADELOCKER_ACCESS_TOKEN, TRADELOCKER_ACC_NUM as environment variables first. Never paste real values into code.
# TRADELOCKER_ACCESS_TOKEN holds the Authorization header that POST /auth/jwt/token returns.
# Replace each {placeholder}, "..." and 0 with a real value before running.
curl -X GET "https://demo.tradelocker.com/backend-api/trade/sessions/{sessionId}" \
  -H "Authorization: Bearer $TRADELOCKER_ACCESS_TOKEN" \
  -H "accNum: $TRADELOCKER_ACC_NUM"

Response

No mock response is recorded for this endpoint. Where the record says why, or names the fields of the reply, it does so in the note at the top of this page. That is a statement about this record, not about what the API returns: read the shape of the reply in the official reference.

TradeLocker API errors you may meet

All TradeLocker API error codes.