GET Tradovate Status
- NT8
- Tradovate
NinjaTrader 8
There is no equivalent NT8 endpoint for Tradovate identity linkage, environment, and token-expiry status.
The Tradovate endpoint on this page is REST-only. The WebSocket API applies to supported NT8 add-on routes, not this Tradovate route.
Link and connection status Tradovate
Returns the link status for your Tradovate identities: whether an identity is linked, its environment (demo or live), and when its access token expires. It is useful as a first call to confirm the Tradovate API is ready before reading or trading.
Endpoint
GET /v1/api/tv/status
Headers
| Name | Value |
|---|---|
| Content-Type | application/json |
| Authorization | Bearer <token> |
Code examples
- Python
- JavaScript
- cURL
import requests
token = 'my-secret-token'
url = "https://app.crosstrade.io/v1/api/tv/status"
headers = {
"Authorization": f"Bearer {token}",
"Content-Type": "application/json"
}
response = requests.get(url, headers=headers)
print(f"Response Code: {response.status_code}, Response Text: {response.text}")
const token = 'my-secret-token';
const url = "https://app.crosstrade.io/v1/api/tv/status";
fetch(url, {
method: "GET",
headers: {
"Authorization": `Bearer ${token}`,
"Content-Type": "application/json"
}
})
.then(res => res.json())
.then(data => console.log(data))
.catch(err => console.error(err));
TOKEN="my-secret-token"
curl -X GET "https://app.crosstrade.io/v1/api/tv/status" \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json"
Response
- 200
- 403
{
"success": true,
"data": {
"linked": true,
"identities": [
{
"environment": "demo",
"userId": "12345",
"expires": "2026-08-01T00:00:00Z"
}
]
}
}
The inner shape is illustrative and may carry additional per-identity fields.
{
"success": false,
"error": "tradovate_not_linked"
}
Platform nuances
Authentication uses the same bearer token as the rest of the CrossTrade API and requires a plan with API access (Pro) plus a linked Tradovate account. Unlinked users receive 403 tradovate_not_linked.
This endpoint is REST-only and has no WebSocket equivalent.