Short answers to the questions that come before the code, and what shipped each week — each linking to the guide with the steps.
Week of 12 October 2026: sign in to fxapis from Claude and ChatGPT, managed copy trading, webhooks that catch up after downtime, and security, data and SDK updates.
Market closed, invalid volume, invalid stops, no margin, wrong symbol: five reasons a broker refuses a valid MT5 order, and how to read and prevent each.
Twelve questions to ask before you build on an MT5 API: platforms, order types, hosting, errors, retries, multi-account trading, security, pricing and docs.
A market order trades now; a pending order waits at the broker for your price. How each behaves in an MT5 API, with one example and a comparison table.
Why a retry or a double click can open two MT5 positions, and how one request identifier — an idempotency key — makes every order safe to send again.
Test an MT5 trading API safely: connect a broker demo account, read from it, place a small demo order and check the result. A test key alone is no sandbox.
Two ways to turn TradingView alerts into MetaTrader 5 trades: an Expert Advisor bridge on a VPS, or a hosted alert URL. Setup, upkeep and failures compared.
The investor password can only watch an MT5 account; the trading password can trade it. Which one your app needs, why the wrong one fails late, and how to ask.
Where to find your MetaTrader 5 server name on desktop, mobile and in your broker's email, why demo and live differ, and the mistakes that break a login.
Where MetaTrader 5 runs, and who keeps it running.
Two ways to turn TradingView alerts into MetaTrader 5 trades: an Expert Advisor bridge on a VPS, or a hosted alert URL. Setup, upkeep and failures compared.
The official MetaTrader5 package needs Windows and a running terminal; a hosted REST API needs neither. Setup, hosting, languages and upkeep compared.
What keeps working when your MetaTrader 5 terminal is closed, what stops, and three ways to keep MT5 automation running without leaving your own computer on.
Local terminal, rented VPS or hosted API: where MT5 automation actually runs, what each setup asks you to maintain, and when a VPS is the right answer.
Logins, passwords, servers and keys — what each one is for.
The investor password can only watch an MT5 account; the trading password can trade it. Which one your app needs, why the wrong one fails late, and how to ask.
Where to find your MetaTrader 5 server name on desktop, mobile and in your broker's email, why demo and live differ, and the mistakes that break a login.
MetaTrader 5 has no API key of its own. Here is what an API key, an MT5 login, a trading password and a server name each do, and where you get each one.
Placing trades that behave, and reading what came back.
Market closed, invalid volume, invalid stops, no margin, wrong symbol: five reasons a broker refuses a valid MT5 order, and how to read and prevent each.
A market order trades now; a pending order waits at the broker for your price. How each behaves in an MT5 API, with one example and a comparison table.
Why a retry or a double click can open two MT5 positions, and how one request identifier — an idempotency key — makes every order safe to send again.
Test an MT5 trading API safely: connect a broker demo account, read from it, place a small demo order and check the result. A test key alone is no sandbox.
What to check before you build on an MT5 API.
Twelve questions to ask before you build on an MT5 API: platforms, order types, hosting, errors, retries, multi-account trading, security, pricing and docs.
The SDKs, examples and starters, and how to use each one.
Install the fxapis TypeScript SDK, connect an MT5 account, place an idempotent market order and handle every failure — from Node.js, with no MetaTrader terminal.
pip install fxapis: connect an MT5 account, place orders that never double-fill, and let the SDK retry only what is safe — from Python on Linux, macOS or Windows.
Three runnable fxapis examples — a quickstart, click-to-trade for signal providers and a trade copier — each in Python, Node.js and curl, against a demo account.
Give Claude, Claude Code, Cursor or VS Code access to your MT5 accounts through fxapis's hosted MCP server — with a scoped key, so the agent can only do what you allow.
Explore the fxapis MT5 API in Postman, send TradingView alerts straight to MT5, and automate trades with n8n — ready-made templates from fxapis-integrations.
A working Next.js app on the fxapis MT5 API: connect an account, watch its positions and place a trade behind a confirm step — with the API key kept on the server.
What shipped each week, with links to the docs.
Week of 12 October 2026: sign in to fxapis from Claude and ChatGPT, managed copy trading, webhooks that catch up after downtime, and security, data and SDK updates.