Skip to main content

Executions

NinjaTrader calls completed order activity executions and exposes it under /v1/api. Tradovate calls the same activity fills and exposes it under REST-only /v1/api/tv routes. NT8 execution calls also support WebSocket RPC. Use the platform tabs on each endpoint page for the matching route and response shape. Tradovate does not provide the single-fill equivalent documented on GET Execution; use its fill-list routes instead.

The path a executions request takes through the CrossTrade API. A bearer token authenticates it, then the route prefix decides which surface handles it: the NinjaTrader path calls through to the add-on inside a running NinjaTrader, while the Tradovate path runs server-side against a linked account with nothing open on the caller’s machine. Reads do not pass the account controls, because they change nothing.

Fills as reported, with real commission. Tradovate session data resets daily.

  • GET Executions: Retrieves execution data from recent history. By default, the last 5 mins of data with a maximum of 15 minutes.
  • GET Execution: Retrieves meta data of a single execution, specific by the execution ID.
  • GET Execution by Order ID: Retrieves all executions or fills associated with a specific order ID.