Skip to main content

What to check when a broker connection fails in Tradecopia

Universal connection checks and broker-specific steps for Rithmic, Tradovate, NinjaTrader, and TopStepX connection failures.

If a broker connection will not establish or keeps disconnecting in Tradecopia, start with the universal checks below before moving to the broker-specific section for your platform.

You might be experiencing this if:

  • A broker connection shows an error or won't connect in Tradecopia

  • You can't get your accounts to appear after adding a connection

  • A connection that was working keeps dropping or disconnecting

  • You're getting a login error or credentials rejected message

Universal checks — try these first for any broker

1. Sign market data agreements on the broker platform

This is the most commonly missed step. Log into your broker's own platform and confirm that all market data agreements are signed. An unsigned agreement causes the API connection to be rejected — Tradecopia cannot connect to an account that has not cleared this step.

2. Confirm your accounts are visible in the broker platform

If your accounts do not appear in the broker's own dashboard, they will not be accessible to Tradecopia. Confirm account status directly with your broker or prop firm before troubleshooting the Tradecopia connection.

3. Confirm you can place orders on the broker side

If your account has margin issues, active restrictions, or is in a restricted state at the broker level, the connection may fail or appear broken even when credentials are correct.

4. Restart Tradecopia

Close the application fully and reopen it. Many transient connection issues — particularly after network events or broker-side resets — resolve on a clean restart.

Rithmic

Rithmic connections have a dedicated setup guide and a dedicated failure resolution article. For Rithmic-specific connection failures, the most common cause by far is an incorrect system name.

Symptom

Where to look

Cannot connect and system name is uncertain

Credentials rejected

Wrong gateway — connection times out

Why is my Rithmic connection failing? — confirm Chicago Area gateway

Connects but no data or no accounts visible

Why is my Rithmic connection failing? — confirm account is Rithmic-issued

On Quantower or multi-feed platform

Why is my Rithmic connection failing? — DXFeed accounts are not supported

Was connecting, now failing intermittently

Contact the Tradecopia support team with your system name, broker, and when the drops occur

Always confirm the system name first before investigating credentials or gateway. The system name is assigned by Rithmic to each prop firm — using the wrong one prevents connection entirely. See the full system name reference table in How to connect your Rithmic account to Tradecopia.

Tradovate and NinjaTrader

Tradovate and NinjaTrader share the same underlying account system. The connection flow is identical for both — authentication happens on the Tradovate side.

Symptom

Where to look

Browser popup did not open

Popup opened but authentication is failing

Why isn't my NinjaTrader connection working? — Tradovate-side auth steps

Prompted to log in every time the app is closed

Connected but wrong accounts showing

Select Demo Account — prop firm accounts (eval and funded) are demo accounts at the broker level

Was connecting, now failing intermittently

Contact the Tradecopia support team with your broker and prop firm details

Account type selection: For prop firm accounts — both eval and funded — select Demo Account, not Live Account. Selecting Live Account causes the wrong accounts to appear after connection.

Market data agreements: Log into your Tradovate account directly and confirm all market data agreements are signed and current. An expired or unsigned agreement will cause connection failures even when credentials are correct.

A single Tradovate connection links all accounts under the same prop firm. If one account is restricted at the broker level, it can affect the visibility of all accounts in that connection.

TopStepX

Note: The large majority of TopStepX connection failures are caused by API key input errors — the key was not fully copied, or the eye icon was not clicked to reveal the full key before copying. Work through the checklist below carefully before assuming a deeper issue.

API key checklist

  • Confirm the API key is linked to your TopStepX account before copying it

  • Click the eye icon to reveal the full key before copying — the key is hidden by default; copying while hidden will copy an incomplete or masked value

  • Paste the key into a plain text editor first to verify it copied cleanly with no missing characters

  • Re-copy directly from the eye-icon-revealed view if in doubt

Username format

TopStepX connections can be sensitive to username format. If the connection is rejected, try each of the following in order:

  1. The username shown on your Topstep.com dashboard

  2. Your email address

  3. The username you use to log in to Topstep.com

Market data agreement

Log into your TopStepX-integrated broker platform and confirm all market data agreements are signed before attempting to connect.

For the full TopStepX setup guide, see How to connect your TopStepX account to Tradecopia.

If you are still not connecting

If all the above steps have been followed and the connection still fails, contact the Tradecopia support team with the following:

  • The broker and prop firm you are connecting

  • A screenshot or description of the error message shown in Tradecopia

  • Confirmation that market data agreements have been signed

  • For Rithmic: your system name and gateway setting

  • For TopStepX: confirmation the API key was revealed with the eye icon before copying

Related articles

Did this answer your question?