CrossTrade Partner Program · Developer guide
Tradovate API access for your app or website.
A script for your own trading account and a product used by hundreds of customers need different kinds of access. If you're building the second, start with the member connection, not just an order endpoint.
CrossTrade Partner integrations are Tradovate-only. No NinjaTrader 8 support.
Which kind of API access do you need?
If you want to trade your own linked accounts from code, CrossTrade's Trading API is available on Pro and above. If you also need to configure your own saved monitors, copiers and other supported settings, the Management API is part of Elite.
Serving your customers is a different integration. Your backend needs to create member accounts, obtain each member's authorization, select the correct token for each request and end access when a member leaves. That is what the CrossTrade Partner Program provides.
| Your goal | CrossTrade access | Platform scope |
|---|---|---|
| Read and trade your own accounts | Trading API, Pro and above | NT8 or Tradovate, using their respective routes |
| Configure your own automation | Management API, Elite | Supported NT8 and Tradovate resources |
| Build a product for customers | Partner API plus delegated Trading and Management access, by invitation | Tradovate only; supported operations within each member's consent |
Direct Tradovate OAuth and CrossTrade Partner access
Registering your own application directly with Tradovate is separate from integrating with CrossTrade. Tradovate controls its own API eligibility and third-party application approvals. Its public developer forum documents the distinction between personal API access and a third-party OAuth application, along with developers' difficulties obtaining the access their products need.
If your direct application is blocked, delayed or declined, you can apply to build on CrossTrade's existing Tradovate integration. Approved partners use a CrossTrade OAuth client. Their members link Tradovate through CrossTrade's hosted Connect page, then authorize the partner application to access supported resources.
Your requests go to CrossTrade's API, using CrossTrade member tokens. You don't receive Tradovate OAuth client credentials or unrestricted access to Tradovate's native API. The practical benefit is that the broker integration and supported automation services are already behind the interface you build against.
For the direct-registration discussion, see Tradovate's third-party OAuth forum thread. Developer posts describe individual experiences; Tradovate determines its current approval policy.
How your application connects a customer
Your backend creates a member with an identifier from your own system. CrossTrade returns a hosted Connect flow. The member links their Tradovate login there and chooses the access your application receives. Your backend exchanges the resulting authorization code for that member's access and refresh tokens.
- 01Create a memberYour backend provisions a CrossTrade seat through the Partner API.
- 02Open hosted ConnectYour member links Tradovate and chooses what your app may access.
- 03Receive authorizationYour backend exchanges the code for that member's scoped tokens.
- 04Power your productCall Trading and supported Management endpoints for that member.
From that point, use the member's token on /v1/api/tv for trading and account reads, and on the supported /v1/api/manage routes for automation settings. Your service's partner token stays on /v1/api/partner for onboarding, membership, usage and lifecycle events. A partner token itself cannot place a trade.
The Partner code guide walks through the flow in Python, JavaScript and cURL. The authentication reference covers scopes, PKCE and refresh-token rotation.
What you can build on top
An account dashboard can show authorized positions, working orders and fills. An order-management interface can place, change and cancel orders. An automation workspace can configure supported Tradovate monitors, copiers and ATM templates, while your application provides the controls your customers see.
Your product can start with read-only access. Trade-capable actions require the corresponding consent and scopes. Management writes are limited to supported delegated resources; your app cannot take over resources created by someone else.
CrossTrade runs the supported Tradovate services in the cloud. Your customers do not need NinjaTrader 8 or a Windows VPS for those services. You still build and operate the backend and interface for your own product.
The boundaries to design around
The Partner API supports Tradovate only. It does not expose NT8 resources, the entire retail Management API, or a market-data feed for charts. Hosted Connect includes CrossTrade's connection and consent experience, so this is an API foundation for your product rather than a ready-made, fully rebranded website.
Each member's grant, the permitted environment and the supported endpoint determine what a request can do. Prop firm customers must have eligible accounts and follow their firm's rules. CrossTrade creates a software account and funds its subscription seat; it does not create or fund a brokerage or evaluation account.
For exact behavior, use the delegated Trading reference and delegated Management reference. Those references cover account selection, write authority and what happens when access ends.
Apply with the product you want to build
Partner access is currently invite-only, with public applications open. Send us your business or project, a website or community link, and the Tradovate workflow you want to offer. You can include your audience size and launch timeline to give us more context.
Partner pricing combines a monthly base fee and metered seat-day usage. We discuss rates and onboarding after reviewing the fit. Your business funds its members' CrossTrade seats and controls the product and pricing it offers its own customers.
