MetaTrader API: All Systems Operational

Safe order retries, stream heartbeat and pending-order events

Add clientOrderId (or an Idempotency-Key header) to /OrderSend or POST /v1/orders: a retry with the same id returns the original result instead of placing a second order. /v1/stream now sends a HEARTBEAT every 10 seconds with the connection state and quote age, an ORDERS event for pending orders, and a POSITIONS + ORDERS snapshot right after every (re)connect. Stream events carry UTC timestamps (timeUtc, timeMscUtc, timeSetupUtc) next to the broker time. /SymbolParams now returns the real stopsLevel and freezeLevel, and /AccountSummary.synced reflects the live connection state. Mistyped broker server names get a one-click suggestion. Details in the API reference.

Completed: planned weekend upgrade

While markets were closed on Sunday, October 11 (18:44 to 20:05 UTC), every API connection was upgraded one at a time; each was unavailable for 15 to 35 seconds and reconnected automatically. Open WebSocket streams were briefly interrupted (a few seconds each) during six restarts of the API gateway that rolled out fixes. No trading session was affected.

Expert Advisor uploads now work with your API key

Upload a compiled EA with POST /EaUpload using the same x-api-key you use everywhere else, attach it with /OpenTerminalChartWithEa and activate it with /Reconnect. The interactive console and the API reference now list the endpoint, plus the live log streams /Logs/OnJournal and /Logs/OnExperts.

Clearer responses, simpler history calls

History endpoints such as /AllHistoryOrders no longer need from/to — omit them and you get the full account history. Error responses now always carry our JSON message instead of a generic gateway page, so you can see exactly what to fix.

Connection insight, market depth and custom EAs

New endpoints give you the MetaTrader Journal and Experts logs (REST and live WebSocket tails), screenshots, Level 2 depth of market with tick data, connection lifecycle calls (/ConnectState, /Reconnect, /Disconnect) and hosted custom Expert Advisors. A Postman collection is available at api.metatraderapi.net/postman.json.

Two-factor authentication for your dashboard

You can now protect your account with an authenticator app. Enable it under Settings in the dashboard.

Resolved: sign-up e-mails delayed for about ten minutes

On the evening of September 8 a batch of scheduled mail briefly queued ahead of new sign-up verification e-mails. Verification and password-reset e-mails are now sent with priority ahead of everything else. No accounts or trading were affected.

Simpler, volume-friendly pricing

Pricing is now a flat rate per connected account with automatic volume discounts as you add more accounts. Full details on the pricing page and in your dashboard.

Resolved: short API interruptions during a planned release

A release that included a new API connection build and a database update caused a few short interruptions on September 3. Connections re-established automatically. Releases are now rolled per account so in-flight requests always finish first.

Resolved: brief API interruption during our infrastructure upgrade

While moving to upgraded infrastructure on September 1 the API was unreachable for a short period until the new TLS configuration was completed. Uptime tracking on this page begins the same day, so that interruption is reflected in the numbers above.

MetaTrader 4 support is fully live

Alongside MT5, you can connect any MetaTrader 4 account and trade it through the same REST + WebSocket API — one login, every quote, order and position as a plain HTTP call. Nothing to keep running on your side.

Security hardening complete

We finished a thorough, top-to-bottom security review: encrypted credentials at rest, strict per-account isolation, rate limiting, full audit logging and automated encrypted backups.

Instant account connections

Your API connection starts warming up the moment you pick your broker, so by the time you enter your login, connecting feels instant.

Lower quote latency

Your API connection now runs in the same region as your broker, trimming the round-trip to a few milliseconds. Faster fills, tighter data.