MetaApi Node.js Alternative for MT4/MT5 SaaS Apps

Node.js is a common choice for high-concurrency fintech backends. Its asynchronous, event-driven model suits many simultaneous HTTP calls and WebSocket streams.

When connecting a Node backend to MetaTrader, many developers start with a vendor SDK. As your user base grows, a plain HTTP integration (a MetaApi JavaScript alternative) keeps your dependency tree small and your code easy to debug.

In this guide we connect Node.js to MT4 and MT5 through MetaTrader API with nothing but the built-in fetch and WebSocket (or the ws package). There is nothing to install on your side, no EA for you to run and no MetaTrader window to keep open. An official Node.js SDK exists too, but it is optional: every call is a plain GET request.

---

1. High-Performance Use Cases for Node.js

A direct MT5 REST API Node.js connection is essential if you are building any of the following data-heavy platforms:

• Copy Trading Panels: Watching one master account's TRADE frames and sending parallel /OrderSend calls to every follower account.
• Prop Firm Dashboards: Streaming open positions with live profit from every challenge account to enforce drawdown rules as they change.
• CRM Trading Dashboards: Integrating MetaTrader metrics directly into Salesforce or HubSpot for sales teams.
• Portfolio Analytics: Fetching massive chunks of historical trade data for frontend visualization.
• AI Trading Bots: Routing algorithmic signals generated by a separate Python microservice through a fast Node.js execution layer.

---

2. Connecting and Authenticating in Node.js

With MetaTrader API there are no connection classes and no provisioning profiles. You connect the trading account once in the dashboard (app.metatraderapi.net): server name exactly as your MetaTrader login window shows it, login, main password. It is usually ACTIVE within 1–2 minutes, and you get two strings: the account id (a UUID) and an API key.

Every call from then on is a plain HTTP GET to https://api.metatraderapi.net/<Endpoint>?id=<accountId> with the key in the x-api-key header. Here is a minimal client using the built-in fetch (Node.js 18+):

const BASE = "https://api.metatraderapi.net";
const KEY = process.env.MT_API_KEY;        // from the dashboard
const ID = process.env.MT_ACCOUNT_ID;      // the account UUID

async function api(path, params = {}) {
  const url = new URL(BASE + path);
  for (const [k, v] of Object.entries({ id: ID, ...params })) url.searchParams.set(k, v);
  // 75 s: the API waits up to 30 s for the account and retries a timed-out read once
  const res = await fetch(url, { headers: { "x-api-key": KEY }, signal: AbortSignal.timeout(75000) });
  if (!res.ok) throw new Error(`${path}: ${res.status} ${await res.text()}`);
  return res.json();
}

const summary = await api("/AccountSummary");
console.log("Equity:", summary.equity, summary.currency);

Need to connect accounts programmatically (a SaaS onboarding flow)? POST https://api.metatraderapi.net/v1/seats with a management key does the same as the dashboard form and returns the account id.

---

3. Executing a Trade (REST API)

Parameters travel as query-string values, and the same call works on an MT4 and an MT5 account. Send a unique clientOrderId with every order: a retry with the same id returns the original result instead of opening a second position.

async function executeTrade() {
  const order = await api("/OrderSend", {
    symbol: "EURUSD",
    operation: "Buy",       // or "Sell", "BuyLimit", "SellStop", ...
    volume: 0.5,            // lots
    stoploss: 1.0850,
    takeprofit: 1.0950,
    magic: 999,
    comment: "Node.js_Trade",
    clientOrderId: `node-${crypto.randomUUID()}`,  // safe to retry with the same id
  });
  // A broker refusal is not an HTTP error: it is HTTP 200, and only
  // state 10009 means done. Any other state is the broker's reason.
  if (order.state !== 10009) throw new Error(`refused: state ${order.state} (${order.comment})`);
  console.log("Filled ticket", order.ticket, "at", order.openPrice);
  return order.ticket;
}

Closing is one more call: api("/OrderClose", { ticket }). Read /OpenedOrders for the authoritative position list.

---

4. Streaming Live Data (WebSockets)

Node.js shines when handling WebSockets. Instead of relying on a MetaApi Node.js alternative that forces you to use their proprietary event listeners, you open one standard WebSocket per account and subscribe to the symbols you care about.

This gives you raw, unfiltered access to live price ticks, position changes and executed deals — perfect for copy trading algorithms and prop firm dashboards.

// Node 22 has a global WebSocket; on Node 18–20: npm i ws
const ws = new WebSocket(`wss://api.metatraderapi.net/v1/stream?apiKey=${KEY}&id=${ID}`);

ws.onopen = () => {
  console.log("Connected to the live stream");
  // Quotes are sent only for subscribed symbols; positions and trades always.
  ws.send(JSON.stringify({ action: "subscribe", symbol: "EURUSD" }));
};

ws.onmessage = (m) => {
  const frame = JSON.parse(m.data);          // { type: "QUOTE" | "POSITIONS" | "TRADE", data: ... }
  if (frame.type === "QUOTE") {
    const q = frame.data;
    console.log(`Live Price [${q.symbol}] - Bid: ${q.bid} | Ask: ${q.ask}`);
  } else if (frame.type === "TRADE") {
    console.log("Deal executed:", frame.data);
  }
};

ws.onclose = () => console.log("Stream disconnected. Implement reconnection logic here.");

---

Conclusion: Keep Your JavaScript Stack Clean

When you build commercial software, fewer dependencies mean fewer things that can break.

With plain HTTP and WebSocket calls your codebase stays small, every request is easy to log and replay, and you keep full control over retries and concurrency.

A seat costs $14 per month (graduated: $13 from the 5th seat, $12 from the 20th); there is no free trial, so test with a broker demo account.

👉 Read the MetaTrader API documentation

---