1. [Home](https://fxapis.com/) 2. / 3. [Solutions](https://fxapis.com/#solutions) 4. / 5. Prop firms Prop firms · Evaluation and funded accounts # Trade and watch every evaluation account through one API. Connect your traders' MT5 accounts, read every position and every deal the broker records, and act on a breach with keys that can close but never open. We host the terminals; your risk engine stays yours. [Get API key ](https://fxapis.com/sign-up)[Talk to us about volume](https://fxapis.com/enterprise) - Trader-side accounts, password sign-in - Deals and positions for risk - Close-only keys Where it fits ## Through the account, not the server. fxapis signs in to each account with its own login, exactly as a trader's terminal would. It does not need access to the broker's server, and it is not the Manager API. That makes it a fit for firms whose evaluation and funded accounts sit at a partner broker: you issue the account, you hold its credentials, and you need to trade it, watch it and — when a rule is breached — flatten it. It works the same way at every MT5 broker that allows password sign-in, so moving traders between brokers does not mean rebuilding your tooling. Firms that run their own MetaTrader 5 server administer it with MetaQuotes' broker interfaces. fxapis complements that rather than replacing it: it gives your platform and your risk tools a clean, scoped REST API into the accounts themselves. | Aspect | fxapis | Manager API | | -------------- | --------------------------------------------------- | --------------------------------- | | Signs in as | Each account, with its own login | The broker's server administrator | | Works with | Accounts at MT5 brokers that allow password sign-in | That broker's server only | | Who can use it | Anyone holding the account credentials | The broker running the server | | Good for | Trading, monitoring, closing | Users, groups, balances | What you get ## The data your risk checks need, and the actions they take. ### Deals, not just orders Every deal the broker recorded — fills, stop-outs, swaps, commissions, deposits — including trades the trader placed from their own MetaTrader app. ### Positions with a timestamp Open positions refresh about every 15 seconds while an account is online, each with observedAt, so a stale view never passes for a current one. ### Close-only keys A trading:reduce key closes positions, moves stops and cancels pending orders — and can never open exposure. Give it to your risk engine. ### Margin before the trade Calculate margin and profit for a proposed order without placing it, to check it against a rule first. ### Many accounts at once Place the same trade on many accounts in one call — for demo challenges, competitions or firm-run strategies. ### Never trapped Closing and cancelling are never refused for billing reasons, whatever happens to your plan. ### The economic calendar for news-time rules High-impact official releases by currency — the same releases many evaluations restrict trading around. Part of [MarketLabs](https://fxapis.com/marketlabs), on the plans that include it. Monitoring ## Read with one key. Act with another. Give each part of your system only what it needs. A dashboard gets a read-only key. Your risk engine gets a `trading:reduce` key: it can close a position the moment a daily loss limit is crossed, but a bug in it can never open one. Only the service that actually places trades holds `trading:execute`. Deals are ordered by the broker's own timestamp and named by type — `buy`, `sell`, `balance`, `commission` — so equity curves and drawdown can be rebuilt from the broker's record rather than from your own requests. A deal with no order of yours behind it is marked as such. Keep monitored accounts in *always connected* mode so positions stay fresh. See [Trading → History](https://docs.fxapis.com/trading#history) and [Authentication → Scopes](https://docs.fxapis.com/authentication). cURL · watch, then act ``` # Everything the broker did on an account since the start of the day — # fills, stop-outs, swaps and commissions, including trades # placed from the trader's own MetaTrader app. curl "https://api.fxapis.com/v1/accounts/$ACCOUNT_ID/deals?since=2026-09-30T00:00:00Z" \ -H "Authorization: Bearer $FXAPIS_READ_KEY" # Open positions, with when they were last seen. curl "https://api.fxapis.com/v1/accounts/$ACCOUNT_ID/positions" \ -H "Authorization: Bearer $FXAPIS_READ_KEY" # A rule was breached: close a position with a close-only key. curl -X POST "https://api.fxapis.com/v1/accounts/$ACCOUNT_ID/positions/$TICKET/close" \ -H "Authorization: Bearer $FXAPIS_REDUCE_KEY" \ -H "Idempotency-Key: breach-7731-$TICKET" \ -H "Content-Type: application/json" -d '{}' ``` Emergency stop ## What a kill switch looks like today. We would rather be precise than impressive here. There is **no self-serve kill switch endpoint** in the API today; fxapis staff can switch trading off for a whole workspace. What you can do yourself, immediately: - **Re-scope or revoke** any key that can open trades. The change applies from that key's next request. - **Flatten** positions and cancel pending orders with a close-only key, account by account, each with an idempotency key. - **Disconnect** an account to take it offline and erase its stored password. Stops live at the broker Stop losses and take profits are held by the broker and fire whether or not the account is online with us. Set them on every trade. FAQ ## Prop firms ask ### Is this the MetaTrader 5 Manager API? No. fxapis is a trader-side API: it signs in to each account with that account's own login, as a trader's terminal would. The Manager API administers a broker's own MT5 server and is licensed to that broker. If your firm runs its own server, you may use both — fxapis for trading and monitoring through accounts, the Manager API for administering the server. ### Can fxapis see trades a trader places from their own MetaTrader app? Yes. The deals endpoint returns everything the broker recorded on the account, including trades placed from the desktop or mobile app, stop-outs, swaps and commissions. Positions show what is open, with the time each snapshot was taken. ### How fresh is position data? Positions refresh about every 15 seconds while an account is online. For accounts you monitor continuously, use always-connected mode. When an account is offline, positions are the last snapshot, and the observedAt field says how old it is. ### Does fxapis enforce drawdown or daily loss rules? No. fxapis gives you the data and the actions — positions, deals, closes and cancellations — and your risk engine decides when a rule is breached. Stop losses and take profits you set live at the broker and fire on their own. ### Is there a kill switch? Not a self-serve one in the API today. fxapis staff can switch trading off for a whole workspace. For your own emergency stop, re-scope or revoke keys that can open trades — a change applies from the key's next request — and use a close-only key to flatten positions and cancel pending orders. ### How many evaluation accounts can we run? Plans are priced per account, from a handful to a thousand connected at once, with demo accounts free up to each plan's allowance — evaluation accounts are usually demo. Beyond that, Enterprise is priced with you. An account whose evaluation has ended can be disconnected, which erases its password and frees its place; its history stays. \> Watch → decide → close ## Connect your first evaluation account. Start on a demo account today, or [talk to us](https://fxapis.com/enterprise) about hundreds of accounts on Enterprise. [Get API key](https://fxapis.com/sign-up) [ ](https://fxapis.com/sign-up) [Trading guide](https://docs.fxapis.com/trading)