Compatibility reference
A platform name, a prop-firm name, and an execution route are not always the same thing. This page identifies the route COPIERA uses and the access each route requires. Availability can change when a broker, prop firm, or API provider changes its permissions.
Production route
Connection method
User-authorized OAuth
COPIERA imports eligible accounts returned by the authorized Tradovate login. Access-token refresh is handled while a valid refresh grant remains available.
Required: A Tradovate account with the API permissions and account access needed for the requested actions.
Production route
Connection method
R | Protocol API
The user selects the matching Rithmic system and gateway, signs in with compatible credentials, and chooses from the accounts returned for that login.
Required: Paid Rithmic access, accepted agreements, order permissions, and a system name that matches the credentials. Demo trials are not compatible with R | Protocol API.
Signal source
Connection method
Authenticated webhook
TradingView alerts can provide normalized entry or exit instructions. TradingView is the signal source; follower execution still uses an authorized broker route.
Required: A valid COPIERA webhook secret, a stable external event ID, an explicit action, quantity, and supported symbol mapping.
Underlying Rithmic route
Connection method
Rithmic credentials
These trading front ends do not require a separate desktop bridge when the underlying account is exposed through a supported Rithmic login.
Required: The broker or prop firm must provide Rithmic credentials and permissions compatible with COPIERA's Rithmic route.
Conditional API route
Connection method
ProjectX API token
COPIERA can validate and route an eligible TopstepX account through ProjectX endpoints when the user's account has compatible API access.
Required: A valid API token, trading account ID, and current provider permission for the requested account and order operations.
Conditional API route
Connection method
CQG WebAPI
COPIERA includes a CQG WebAPI route for provisioned accounts. Availability is determined by the account provider and CQG application entitlements.
Required: Compatible CQG credentials, gateway access, account resolution, and order permissions.
Provider-specific
Connection method
Broker API or authenticated bridge
These names cover multiple provider deployments. A route is available only when the specific broker or prop firm exposes a compatible endpoint and COPIERA configuration.
Required: Confirm the exact broker deployment with COPIERA before relying on the route for live trading.
Supported means COPIERA has an implemented connection path. It does not mean every account sold under a platform or prop-firm brand has API permission. Validate the exact login, system, account, and order route before using a funded or live account.