Tradovate 'Not Found: md/subscribeQuote' Fix

Your auth flow worked, your account socket is humming along, and then you fire off a md/subscribeQuote to start streaming live prices and the server hands you back Not found: md/subscribeQuote, often mangled into something like "\"Not found: md/subscribeQuote\"" with escape characters piled on. The endpoint is right there in the docs. So why does Tradovate act like it doesn't exist?

Here's the short version: you sent the request to the wrong WebSocket. Quote subscriptions don't live on the same connection you use to sync your account or place orders. Fix which socket the request goes to and the error clears. Let's walk through exactly why this happens, how to route it correctly, and what tends to break next once the frame finally lands.

What “Not Found” Actually Means Here

Treat this like a 404 on a REST call. A 404 says the URL path doesn't exist on that server. Over Tradovate's WebSocket the logic is identical: every frame you send names an endpoint, and if the socket you're connected to doesn't serve that endpoint, the server replies Not found with the endpoint name echoed back at you.

Read that carefully, because it rules a lot out. It's not telling you your symbol is bad. It's not telling you your token expired. It's not telling you your JSON is malformed. It's telling you one thing: “there's no route for md/subscribeQuote on this connection.” And there's exactly one common reason for that.

The Cause: You're on the Account Socket, Not the Market-Data Socket

Tradovate runs two separate WebSocket services, and they are not interchangeable. People wire up the first one, get it authorized, watch account and order data flow perfectly, and then assume that same connection handles everything. It doesn't.

• The account / API socket handles orders, positions, fills, account sync, and the rest of the entity data. This is where user/syncRequest, order/placeOrder, and account/list belong. Live is wss://live.tradovateapi.com/v1/websocket; demo is wss://demo.tradovateapi.com/v1/websocket.
• The market-data socket handles live prices, quotes, the DOM, charts, histograms. This is where every md/ endpoint lives, including md/subscribeQuote, md/subscribeDOM, and md/getChart. Live is wss://md.tradovateapi.com/v1/websocket; demo is wss://md-demo.tradovateapi.com/v1/websocket.

Send md/subscribeQuote to the account socket and there's simply no matching route, so back comes Not found: md/subscribeQuote. The account socket won't drop a hint that you're knocking on the wrong door, it just reports the endpoint as missing. Here's the full host map so you can line up your environment:

The Fix: Open and Authorize a Second Socket for Quotes

You don't move your account socket. You add a market-data socket alongside it. Keep the account connection for orders and sync; open a brand-new WebSocket to the market-data host for prices. Here's the sequence that clears the error.

Authorize frame:
authorize
1

<yourMdAccessToken>

Subscribe frame:
md/subscribeQuote
2

{"symbol":"ESU6"}

Subscribe Once Per Symbol, Not in Bulk

A quick trap worth naming: md/subscribeQuote takes a single symbol per call. There's no array form where you hand it a list and get everything at once. If you want to follow ES, NQ, and CL together, send three separate subscribe frames over the same market-data socket, each with its own request id. One socket can carry many live quote subscriptions at the same time, you just register them one at a time. When you're done with a contract, unsubscribe with md/unsubscribeQuote so you're not paying to receive a stream you no longer read.

What Breaks Next: the Socket's Right, But No Prices Show

Once the not-found error clears, the next class of problem is different in nature. The request reaches the market-data engine now, so any failure from here is about what you asked for and whether you're entitled to it, not about a missing route.

“Symbol is inaccessible”

If the subscribe call comes back with an inaccessible or unknown-symbol response, two things are usually in play. First, the symbol has to be a real, fully qualified front-month contract, ESU6, not the bare ES root, and not a contract that already expired and rolled to the next quarter. Second, your account needs the entitlements to see that data at all: the Contract Library plus an active exchange market-data subscription. Without those, a perfectly formed request still returns nothing usable. This is a distinct issue with its own fix.

The socket keeps dropping

Tradovate's WebSocket expects a periodic heartbeat. If you connect, authorize, subscribe, and then go quiet, the server closes the connection and your quotes stop cold. Send an empty heartbeat frame on the interval Tradovate specifies (a short one, on the order of a couple of seconds) so the market-data socket stays open for as long as you need prices. A lot of “it worked for a minute then died” reports trace straight back to a missing heartbeat.

The token expired mid-session

Access tokens don't last forever. If your market-data socket authorized fine at the start of the session and later stops responding, your token may simply have aged out. Renew it before it expires rather than waiting for calls to fail, then re-authorize the socket with the fresh token.

A Quick Checklist to Clear the Error

Skip the Raw Socket Wiring

Most people who hit Not found: md/subscribeQuote aren't chasing a data-vendor project, they just want a strategy to trade on Tradovate without babysitting two sockets, two tokens, heartbeats, and frame formats. If that's you, there's a much shorter path than hand-coding the whole WebSocket layer.

For the problems that tend to show up right after this one, these guides go deeper: if your symbols come back inaccessible rather than not-found, that's a separate entitlement and symbol-format issue; to get real-time prices flowing in the first place, subscribing to Tradovate real-time market data is the starting point; and if your socket authorizes fine then quietly stops answering, that's usually the 90-minute access token expiring mid-session.