> For the complete documentation index, see [llms.txt](https://docs.trada.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trada.io/developers/platform-integration.md).

# Platform integration reference

How each supported platform connects — credentials versus secure sign-in.

Trada connects to trading accounts you already hold on nine supported platforms. Every connection uses one of two methods: **credentials** entered in Trada, or **secure sign-in** (OAuth) authorized on the platform's own page.

<figure><img src="https://1071438488-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOsaVyFC53CtoAY5kabHr%2Fuploads%2Fgit-blob-441ccb447871812b8bf8dfc81b0c57503326e703%2Fintegration-matrix.svg?alt=media" alt="Platform integration table"><figcaption><p>How each platform integrates — market, authentication, and capabilities.</p></figcaption></figure>

## Compare the two connection methods

* **Credentials** — You supply the account's connection details (login, server, or API key, depending on the platform) through Trada's **Add Account** flow. Any API keys or tokens a platform requires are held as a credential set and attached to the connection.
* **Secure sign-in (OAuth)** — Trada redirects you to the platform's own authorization page. You approve access there, and the platform returns an authorization token to Trada. Your platform password is never entered into Trada. This method currently applies to **cTrader**.

{% hint style="info" %}
Credential sets are managed under **Credential Sets** (`/credential-sets`) before being attached to a connection. OAuth authorization lives at `/credential-sets/oauth`. You normally arrive at either from the **Add Account** dialog when the selected platform needs it.
{% endhint %}

## Reference the platform matrix

| Platform     | Market      | Connection method      | Notes                                                          |
| ------------ | ----------- | ---------------------- | -------------------------------------------------------------- |
| MetaTrader 4 | Forex / CFD | Credentials            | Connectable for journaling and reporting; not a copier source. |
| MetaTrader 5 | Forex / CFD | Credentials            | —                                                              |
| cTrader      | Forex / CFD | Secure sign-in (OAuth) | Authorized on cTrader's own page.                              |
| TradeLocker  | Forex / CFD | Credentials            | —                                                              |
| DXTrade      | Forex / CFD | Credentials            | —                                                              |
| MatchTrader  | Forex / CFD | Credentials            | —                                                              |
| NinjaTrader  | Futures     | Credentials            | —                                                              |
| Rithmic      | Futures     | Credentials            | —                                                              |
| DXFeed       | Futures     | Credentials            | —                                                              |

The partner list of prop firms and brokers behind these platforms is expanding; platform support above is fixed at nine.

## Connect a credential-based platform

{% stepper %}
{% step %}

### Open Add Account

From **Accounts**, select **Add Account** and choose your platform.
{% endstep %}

{% step %}

### Enter connection details

Provide the login, server, or API key the platform requires. Where a credential set is needed, it is stored under **Credential Sets** and attached to this connection.
{% endstep %}

{% step %}

### Confirm the connection

Trada establishes the link and the account moves to **Connected**. Balance and status populate on the first sync.
{% endstep %}
{% endstepper %}

## Connect cTrader with secure sign-in

{% stepper %}
{% step %}

### Choose cTrader

From **Add Account**, select **cTrader**.
{% endstep %}

{% step %}

### Authorize on cTrader

Trada redirects you to cTrader's secure sign-in page. Approve access there. Your cTrader password stays with cTrader — it is never entered into Trada.
{% endstep %}

{% step %}

### Return to Trada

cTrader returns an authorization token and you land back in Trada with the account connecting automatically.
{% endstep %}
{% endstepper %}

## Handle the Forex and Futures difference

* **Forex / CFD** connections are flat: one connection equals one trading account.
* **Futures** connections are nested: one login pulls in multiple trading accounts. Each trading account has an **Enable** toggle, and only enabled accounts count toward plan limits. You cannot manually add or delete individual futures trading accounts — only rename and enable or disable them.

{% hint style="warning" %}
A connection's platform is read-only after the account is added. To move an account to a different platform, delete it (two-step confirmation) and add it again under the new platform.
{% endhint %}

{% hint style="info" %}
Trada does not yet offer a public API for programmatic connection. See [API access](/developers/api-access.md) for current status.
{% endhint %}

## Related

* [Supported platforms](/connecting-accounts/supported-platforms.md)
* [Connecting accounts](/connecting-accounts/connecting-accounts.md)
* [API access](/developers/api-access.md)
* [Copy trading](/copy-trading/copy-trading.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trada.io/developers/platform-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
