Developer access
TradeCopier API reference and connection guide
Connect an account with the reviewed app steps below, then use the reviewed read-endpoint reference to plan an integration. Confirm your plan access and deployed API contract before sending trading instructions.
What to verify before you build
Platform support and dashboard features do not, by themselves, establish API capabilities. Use the current account-specific reference to answer these four questions.
Step 1
Confirm access for your plan
The published Pro and Pro Plus plans list API Access. Ask which current API version, account types and permissions your subscription actually includes before designing a live integration.
Step 2
Use the reviewed endpoint reference
Start with the read endpoints below. They were checked against the October 2 backend source revision. Confirm the deployed contract and subscription access with support before using write actions.
Step 3
Agree on authentication and limits
Confirm how credentials are issued and revoked, which scopes are required, how rate limits are reported, and what to do after authorization or availability errors. Never put a live token in an email or public support request.
Step 4
Test outcomes before live use
Ask whether a demo environment is available for your route. Record request IDs, timestamps, API responses and the destination broker's actual orders, fills and positions; an accepted request is not proof of a completed trade.
Account connection steps
Reviewed October 2, 2026 against the account-connection interface. These steps document MT5, TradeLocker and cTrader connection flows. TradeCopier also lists MT4, NinjaTrader 8, DXTrade, MatchTrader and VertexFX; request the current connector instructions for those platforms and your exact source-to-follower route. A connection flow does not establish every account type or order action.
MetaTrader 5
In the app's Add Account flow, choose MetaTrader 5, search for the broker server, and enter your login ID and trading password. Confirm the exact server and account connection before assigning it to a copier group.
TradeLocker
Choose TradeLocker and the Demo or Live environment, select the broker or enter the server, and enter the account email and password. If more than one account is returned, select the intended account and verify its account number.
cTrader
Choose cTrader, open the authorization window, approve the intended account access, and select the returned account. Allow the app's authorization popup and verify the account and environment before connecting it to a group.
Reviewed read-endpoint reference
Reference revision: October 2, 2026, backend commit 2a3144e. These routes are defined in the reviewed implementation; authenticated production responses were not tested for this documentation. The API origin is https://api.tradecopier.org. All routes below require a valid signed-in user bearer token in the Authorization header. An account ID is a resource identifier, not an authorization credential.
GET /api/trading-accountsList the signed-in user's TradeLocker account records. Returns { success: true, data: [...] }.
GET /api/trading-accounts/{id}/capabilitiesRead the selected account adapter's capabilities before choosing an action.
GET /api/trading-accounts/{id}/positionsRead positions for a TradeLocker account owned by the signed-in user.
GET /api/trading-accounts/{id}/ordersRead TradeLocker orders. Optional filters: from, to and instrumentId.
GET /api/ctrader/accountsList the signed-in user's connected cTrader account records.
GET /api/ctrader/accounts/{id}/positionsRead positions for the selected owned cTrader account.
Read request example
In your approved API client, send GET /api/trading-accounts with Authorization: Bearer <your-token> and Accept: application/json. The placeholder is illustrative; never publish a real token or include it in a support message.
Errors, limits and unknown trade outcomes
The reviewed TradeLocker adapter returns 400 for invalid requests, 401 for authentication failures, 404 for unavailable owned resources, 429 for rate limiting, 503 for read timeouts or network errors, and 502 for other upstream failures. Inspect the returned code, error and requestId when available. These mappings do not establish the error contract for every API route.
Account-connection requests are limited to three per five-minute window per authenticated user in this source revision. A rejected request returns 429 and Retry-After when available. Read routes may also encounter upstream limits; this is not a published universal read quota. Respect retry instructions.
A TradeLocker write timeout can return 409 with write_outcome_unknown. Reconcile actual broker orders and positions before retrying a trading action. A response or an account connection is not proof of a completed trade. cTrader can return 409 with reconnect_required when OAuth reconnection is needed.
Questions to send with your request
- Which documented API version and environment apply to my plan?
- Which read and write actions are supported for my platform and account route?
- What authentication scopes, credential rotation steps and rate limits apply?
- How are retries, duplicate requests, rejected orders and unknown outcomes identified?
- Is a demo environment available for my intended order actions?
- Which response fields can I reconcile with broker orders and final positions?
Share the platform pair and intended workflow with support, but keep account credentials and API tokens out of the request. For the current public plan limits, see pricing.
