🔌 Find the 32-bit MT4 methods — right from the main page
A handful of MT4 ManagerAPI calls have to run inside a 32-bit process and live on a separate companion host — the x86 sidecar. Until now, the main API page never pointed to it, so it was easy to miss.
What's new:
• The main API landing page now links straight to the x86 sidecar
• A clear breakdown of what it serves — Messaging, Plugins, Batch snapshots, Plugin commands
• Same OAuth token, same
👉 Live on Sandbox: pre-x86.mywebapi.com
A handful of MT4 ManagerAPI calls have to run inside a 32-bit process and live on a separate companion host — the x86 sidecar. Until now, the main API page never pointed to it, so it was easy to miss.
What's new:
• The main API landing page now links straight to the x86 sidecar
• A clear breakdown of what it serves — Messaging, Plugins, Batch snapshots, Plugin commands
• Same OAuth token, same
tradePlatform id, same /api/v2/MT4/… path — only the host differs👉 Live on Sandbox: pre-x86.mywebapi.com
🔜 MT5 v2 API — coming soon
A new v2 REST + real-time API for MetaTrader 5 is on the way — the same clean, modern contract as our MT4 v2. It's currently in staging for early testing; the production rollout will follow.
What's coming:
• Unified JSON envelope
• Configuration — read & partially update users, groups and symbols; read server time and manager info. Partial updates use JSON Merge Patch: send only the fields you want to change.
• Trading data — list positions, deals and orders by group, with cursor-based pagination.
• Real-time over SignalR (
Client SDKs (TypeScript, .NET, Python, PowerShell) are on the way too. Stay tuned for the production release.
A new v2 REST + real-time API for MetaTrader 5 is on the way — the same clean, modern contract as our MT4 v2. It's currently in staging for early testing; the production rollout will follow.
What's coming:
• Unified JSON envelope
{data, error, meta} — predictable success/error handling; every response is HTTP 200 with errors in the body.• Configuration — read & partially update users, groups and symbols; read server time and manager info. Partial updates use JSON Merge Patch: send only the fields you want to change.
• Trading data — list positions, deals and orders by group, with cursor-based pagination.
• Real-time over SignalR (
/hubs/mt5/v2) — connection status and margin-call / stop-out events.Client SDKs (TypeScript, .NET, Python, PowerShell) are on the way too. Stay tuned for the production release.
🚀 New: official TypeScript / JavaScript SDK for the MyWebAPI MT4/MT5 API
Build broker integrations in minutes — install one package and you're connected:
What you get
• Full API coverage — every MT4 and MT5 v2 endpoint, fully typed.
• Real-time built in — stream live ticks, trades and margin calls over SignalR from the same client.
• Auth on autopilot — OAuth2 tokens are acquired, cached and refreshed for you; just pass your API key.
• Zero-friction start — auto-detects your trading platform; runs in Node, Bun, Deno, the browser and edge runtimes.
Open source (MIT) — source, examples and docs on GitHub:
github.com/CPlugin/mywebapi.com-sdk-js
Available now. Happy building! 🛠️
Build broker integrations in minutes — install one package and you're connected:
npm install @mywebapi.com/sdkWhat you get
• Full API coverage — every MT4 and MT5 v2 endpoint, fully typed.
• Real-time built in — stream live ticks, trades and margin calls over SignalR from the same client.
• Auth on autopilot — OAuth2 tokens are acquired, cached and refreshed for you; just pass your API key.
• Zero-friction start — auto-detects your trading platform; runs in Node, Bun, Deno, the browser and edge runtimes.
Open source (MIT) — source, examples and docs on GitHub:
github.com/CPlugin/mywebapi.com-sdk-js
Available now. Happy building! 🛠️
🔥1
The new cplugin.com is live
We have rebuilt our website from the ground up — same address, brand-new experience:
• Faster everywhere — a lean, modern build; pages open in a blink on desktop and mobile.
• Products, clarified — every plugin and tool now carries a concise summary, so you can tell in seconds whether it fits your brokerage.
• Documentation, reorganized — full navigation across all records, refreshed guides for MT4/MT5 server plugins, Manager API and WebAPI.
• Same heritage — an engineering house for server-side MetaTrader software: in forex since 2006, CPlugin since 2015.
Take a look: https://cplugin.com
Questions? We are one message away: https://cplugin.com/contact
We have rebuilt our website from the ground up — same address, brand-new experience:
• Faster everywhere — a lean, modern build; pages open in a blink on desktop and mobile.
• Products, clarified — every plugin and tool now carries a concise summary, so you can tell in seconds whether it fits your brokerage.
• Documentation, reorganized — full navigation across all records, refreshed guides for MT4/MT5 server plugins, Manager API and WebAPI.
• Same heritage — an engineering house for server-side MetaTrader software: in forex since 2006, CPlugin since 2015.
Take a look: https://cplugin.com
Questions? We are one message away: https://cplugin.com/contact
🔥1
🚀 .NET SDK — now on NuGet
Integrate our trading platform management API into any .NET application in minutes:
• One generated method per API endpoint — full v2 coverage
• Automatic OAuth2 token management: acquire, cache, refresh — zero boilerplate
• Real-time streaming over SignalR
• Cursor pagination built in
• Targets .NET Standard 2.0 and .NET 8 — works from C#, F# and VB
Docs & examples: github.com/CPlugin/mywebapi.com-sdk-dotnet
The JavaScript/TypeScript SDK is already on npm (
Integrate our trading platform management API into any .NET application in minutes:
dotnet add package MyWebApi.Sdk• One generated method per API endpoint — full v2 coverage
• Automatic OAuth2 token management: acquire, cache, refresh — zero boilerplate
• Real-time streaming over SignalR
• Cursor pagination built in
• Targets .NET Standard 2.0 and .NET 8 — works from C#, F# and VB
Docs & examples: github.com/CPlugin/mywebapi.com-sdk-dotnet
The JavaScript/TypeScript SDK is already on npm (
@mywebapi.com/sdk), Python is next.📬 Email delivery reliability improved
We found and fixed an issue that could cause invitation emails — like resending a team invite — to fail to send.
The fix is live now. If you tried resending an invitation recently and it did not go through, please give it another try — it will work now.
Thanks for your patience. We are always working to make the platform more reliable for you.
We found and fixed an issue that could cause invitation emails — like resending a team invite — to fail to send.
The fix is live now. If you tried resending an invitation recently and it did not go through, please give it another try — it will work now.
Thanks for your patience. We are always working to make the platform more reliable for you.
🚀 PowerShell SDK for MyWebAPI.com is here
Manage your trading platform straight from PowerShell. The new MyWebApi module is now on the PowerShell Gallery:
What's inside
• Full REST v2 coverage — every endpoint as an idiomatic cmdlet (
• Real-time streaming over SignalR — live ticks, trades, margin calls and status
• OAuth2 built in — connect once, tokens refresh automatically
• Cursor pagination, idempotency keys and platform discovery out of the box
Cross-platform on PowerShell 7.4+ (Windows · Linux · macOS).
GitHub · PowerShell Gallery
Manage your trading platform straight from PowerShell. The new MyWebApi module is now on the PowerShell Gallery:
Install-Module MyWebApiWhat's inside
• Full REST v2 coverage — every endpoint as an idiomatic cmdlet (
Get-… / Invoke-… / Update-…)• Real-time streaming over SignalR — live ticks, trades, margin calls and status
• OAuth2 built in — connect once, tokens refresh automatically
• Cursor pagination, idempotency keys and platform discovery out of the box
Cross-platform on PowerShell 7.4+ (Windows · Linux · macOS).
GitHub · PowerShell Gallery
❤1
PayPal checkout that never leaves you hanging
A small change with a real, everyday difference: your PayPal payment links now stay reliable — even if you come back to an invoice hours later.
Before, a PayPal checkout link had a short shelf life. Open an invoice, get pulled away, come back later to pay — and the old link could quietly stop working, with no obvious way forward.
Now, when you click Pay with PayPal, we check the link on the spot and, if it's no longer good, prepare a fresh secure checkout and take you straight to it. And we only ever charge what's actually left owing on the invoice — so a partial payment, or switching how you pay midway, never risks paying twice.
No settings, no surprises. Paying just works, whenever you choose to.
A small change with a real, everyday difference: your PayPal payment links now stay reliable — even if you come back to an invoice hours later.
Before, a PayPal checkout link had a short shelf life. Open an invoice, get pulled away, come back later to pay — and the old link could quietly stop working, with no obvious way forward.
Now, when you click Pay with PayPal, we check the link on the spot and, if it's no longer good, prepare a fresh secure checkout and take you straight to it. And we only ever charge what's actually left owing on the invoice — so a partial payment, or switching how you pay midway, never risks paying twice.
No settings, no surprises. Paying just works, whenever you choose to.
Temporary Toolbox backend outage
The Toolbox user interface is still available, but its backend is currently not responding. Some features may be unavailable or fail to load while we work on restoring the service.
We will post another update when the backend is operational again.
The Toolbox user interface is still available, but its backend is currently not responding. Some features may be unavailable or fail to load while we work on restoring the service.
We will post another update when the backend is operational again.
Backend appears to be working again.
Thanks for your patience and understanding while we worked through the issue.
Thanks for your patience and understanding while we worked through the issue.
The v2 API is in open beta — and there are SDKs now
Two things shipped, and the second matters more than the first if you run MT5.
Where it runs. v2 is on the sandbox only — it answers on
What changes. One response envelope for every call —
What it covers — the actual numbers.
• MT4: 147 endpoints in v2 against 42 in v1 — a real expansion, including configuration and management surfaces v1 never exposed.
• MT5: 12 endpoints, all read-only, against 54 in v1. Not there yet.
If your integration is MT5, stay on v1 — it has more of what you need and it is the version running in production anyway. v1 stays stable and fully supported, with no deadline.
Three SDKs, open source.
•
•
•
Each one acquires, caches and refreshes OAuth2 tokens for you, streams real-time over the same client, and has cursor pagination built in. Whatever your team wrote to do those things, you can probably delete.
Two caveats worth stating plainly: they target v2 only, so an existing v1 integration cannot swap a package in and keep working; and they are at 0.x, so pin a version. A Python SDK is in progress and not published yet.
Full write-up, numbers included
Two things shipped, and the second matters more than the first if you run MT5.
Where it runs. v2 is on the sandbox only — it answers on
pre.mywebapi.com, while production still serves v1 and nothing else. Build and evaluate against it today; don't move a live integration onto it yet.What changes. One response envelope for every call —
data, error, meta — with a plain HTTP 200, so you read the error field instead of juggling status codes. The version sits in the path. Serialization is source-generated. Real-time for ticks, margins and trade events runs over SignalR with automatic reconnect.What it covers — the actual numbers.
• MT4: 147 endpoints in v2 against 42 in v1 — a real expansion, including configuration and management surfaces v1 never exposed.
• MT5: 12 endpoints, all read-only, against 54 in v1. Not there yet.
If your integration is MT5, stay on v1 — it has more of what you need and it is the version running in production anyway. v1 stays stable and fully supported, with no deadline.
Three SDKs, open source.
•
@mywebapi.com/sdk — npm, Node.js and browsers•
MyWebApi.Sdk — NuGet, .NET•
MyWebApi — PowerShell GalleryEach one acquires, caches and refreshes OAuth2 tokens for you, streams real-time over the same client, and has cursor pagination built in. Whatever your team wrote to do those things, you can probably delete.
Two caveats worth stating plainly: they target v2 only, so an existing v1 integration cannot swap a package in and keep working; and they are at 0.x, so pin a version. A Python SDK is in progress and not published yet.
Full write-up, numbers included
🔍 How the copier proves it stayed in sync
A trade copier is only trustworthy if it can prove nothing drifted. We wrote up how Toolbox's reconciliation engine actually works:
• Two checks, not one — Open Trades Reconciliation (live) catches missed and orphan positions as they happen; Closed Trades Reconciliation looks back over any date range, preview or execute
• Failed Operations view — see exactly why a copy attempt didn't go through, no log-grepping
• Loop check, fixed twice — the DFS-based cycle detector was too aggressive with group-masked configs; both false-positive cases are gone
• Reports that don't lie about their own scope — a
Works across MT4, MT5 and MatchTrader — including the partial-close ticket tracking that has to translate between platforms with different conventions.
Full breakdown: read the article
A trade copier is only trustworthy if it can prove nothing drifted. We wrote up how Toolbox's reconciliation engine actually works:
• Two checks, not one — Open Trades Reconciliation (live) catches missed and orphan positions as they happen; Closed Trades Reconciliation looks back over any date range, preview or execute
• Failed Operations view — see exactly why a copy attempt didn't go through, no log-grepping
• Loop check, fixed twice — the DFS-based cycle detector was too aggressive with group-masked configs; both false-positive cases are gone
• Reports that don't lie about their own scope — a
Snapshot indicator now freezes the filter context a report was generated withWorks across MT4, MT5 and MatchTrader — including the partial-close ticket tracking that has to translate between platforms with different conventions.
Full breakdown: read the article
Ask your trade platforms a question
We have opened an experiment in the Toolbox sandbox: an assistant that answers questions about your MT4, MT5 and MatchTrader servers in plain language.
"How many accounts are in the real groups?"
"What is the net exposure by symbol?"
"Compare the EURUSD settings on these two servers."
It reads the platform and answers — and every answer shows the exact lookups behind it, so a number you doubt is a number you can check rather than one you have to trust.
It only reads. Nothing you ask can change a platform, an account or a setting — not because a rule forbids it, but because no such capability exists in the build.
Try it: pre.toolbox.cplugin.com → Assistant
If you administer your organisation you will find it in the menu straight away. If you are a member, your admin grants access under Settings → Members.
Fair warning, and we mean it. This is an early experiment: it may change or be withdrawn, answers can be wrong or unavailable, there are no service guarantees yet, and we have not set a price for it. Capacity is deliberately small while we learn — if an answer does not come back, that is us, not you; wait a moment and ask again.
What we would most like are the awkward questions — the ones you would actually ask a colleague at the end of a long session, where the answer lives across three platforms at once. Tell us what you asked and what you wished it could answer. That is what decides whether this becomes a real part of Toolbox.
We have opened an experiment in the Toolbox sandbox: an assistant that answers questions about your MT4, MT5 and MatchTrader servers in plain language.
"How many accounts are in the real groups?"
"What is the net exposure by symbol?"
"Compare the EURUSD settings on these two servers."
It reads the platform and answers — and every answer shows the exact lookups behind it, so a number you doubt is a number you can check rather than one you have to trust.
It only reads. Nothing you ask can change a platform, an account or a setting — not because a rule forbids it, but because no such capability exists in the build.
Try it: pre.toolbox.cplugin.com → Assistant
If you administer your organisation you will find it in the menu straight away. If you are a member, your admin grants access under Settings → Members.
Fair warning, and we mean it. This is an early experiment: it may change or be withdrawn, answers can be wrong or unavailable, there are no service guarantees yet, and we have not set a price for it. Capacity is deliberately small while we learn — if an answer does not come back, that is us, not you; wait a moment and ask again.
What we would most like are the awkward questions — the ones you would actually ask a colleague at the end of a long session, where the answer lives across three platforms at once. Tell us what you asked and what you wished it could answer. That is what decides whether this becomes a real part of Toolbox.
WebAPI: ten minutes down on 29 September — and what changed overnight
Yesterday 15:47–15:57 UTC the WebAPI node in Germany stopped answering. One MT4 call hung inside the trading server for 11 minutes, every other call queued behind it, and the node ran out of workers — health checks included.
Fixed in production, every region, the next morning:
• a deadline on every trading-server call (trades 5 s, reads 10 s, history 30 s), your own per request via
• timeouts say what they mean:
• a stuck connection is replaced, the rest keep flowing
• safe trade retries with
• failover within about a minute, not several
Timeline, cause and what to do on your side:
https://cplugin.com/blog/webapi-outage-29-september-what-changed?utm_source=telegram&utm_medium=social&utm_campaign=webapi-outage-29-september-what-changed
Yesterday 15:47–15:57 UTC the WebAPI node in Germany stopped answering. One MT4 call hung inside the trading server for 11 minutes, every other call queued behind it, and the node ran out of workers — health checks included.
Fixed in production, every region, the next morning:
• a deadline on every trading-server call (trades 5 s, reads 10 s, history 30 s), your own per request via
X-Request-Timeout• timeouts say what they mean:
Timeout, OutcomeUnknown, Busy• a stuck connection is replaced, the rest keep flowing
• safe trade retries with
Idempotency-Key• failover within about a minute, not several
Timeline, cause and what to do on your side:
https://cplugin.com/blog/webapi-outage-29-september-what-changed?utm_source=telegram&utm_medium=social&utm_campaign=webapi-outage-29-september-what-changed