A Simpler Alternative to the Tradovate API

What makes the direct Tradovate API hard

Using Tradovate's own API means obtaining an access token, renewing it before it expires, keeping a WebSocket alive for live data, and handling disconnects without losing track of orders. For a trading bot or a TradingView bridge, that connection code often ends up larger than the strategy itself.

Signal Trade App keeps the broker connection open on its side. You call a REST endpoint with an API key, and we handle the broker session, symbol resolution and reconnection.

Authentication and scopes

Create a key on the API Keys page (/api-keys) and send it in the X-API-Key header on every request. A key has scopes. A read key can list accounts, positions and orders. A trade key can place, modify and cancel orders, set protection and flatten. A missing or invalid key returns 401, and a key without the needed scope returns 403.

Endpoints you will use

All paths sit under /api/v1.

• GET /accounts lists your accounts with broker, environment, status and balance.
• GET /accounts/:id/positions and GET /accounts/:id/risk read exposure and risk state.
• GET /accounts/:id/orders returns closed trade history from our records.
• GET /accounts/:id/working-orders returns the live order book from the broker.
• POST /accounts/:id/orders places an order. PUT and DELETE on /accounts/:id/orders/:orderId modify or cancel one.
• POST /accounts/:id/protect attaches take-profit and stop-loss to an open position.
• DELETE /accounts/:id/positions flattens the account.
• POST /webhooks creates a webhook URL for an account.
• GET /stream is a Server-Sent Events stream of orders, fills, positions, balances and trailing drawdown, so you do not have to poll.
• GET /connection-health/stream is a Server-Sent Events stream of connection status.

A short order example

To place a bracketed market buy, send a POST to /api/v1/accounts/:id/orders with your X-API-Key header and a JSON body containing symbol, action, qty, orderType and either takeProfit and stopLoss or a bracket object. A successful call returns 201 with the order id. Action and order type are accepted in any case, and price is required for limit and stop orders.

If the broker refuses an order, you get a 502 with the code BROKER_ORDER_REJECTED and the broker's reason. An unresolvable symbol returns a 400 with the code UNKNOWN_SYMBOL. If the entry is placed but a bracket leg is refused, you get a 409 with the code BRACKET_INCOMPLETE and the order id, so you inspect the position instead of resubmitting.

Idempotency, retries and limits

Send an Idempotency-Key header of 8 to 128 characters with an order. If you retry with the same key within 24 hours, you get the stored response back instead of a second order. That matters when a network timeout leaves you unsure whether the first request landed.

Requests are limited to 120 per minute per API key, and going over returns 429. Orders that open exposure are refused while trading is paused on your account, and an inactive account returns a 403 until you reconnect the broker. Quote and candle endpoints are disabled for API consumers, so bring your own market data.

Tradovate and Rithmic

The same endpoints work on accounts connected through Tradovate or Rithmic, and the account list reports the broker for each one. Order routing runs under 50ms on Tradovate and under 5ms on Rithmic. Accounts are addressed by their Signal Trade App id, so your code does not change when you add a broker.