EST. 2015

MyWebApi v2 is live in production — here's what to build against now

The v2 REST API is no longer sandbox-only. For MT4 it's the recommended path going forward — 147 endpoints against v1's 42. For MT5, v2 covers 12 endpoints, including partial updates of user, group and symbol records; full MT5 integrations should stay on v1 for now.

Three weeks ago v2 was sandbox-only, and I said this would get its own announcement once it reached production. It has.

v2 now answers on `cloud.mywebapi.com`

Same envelope, same SDKs, same everything we told you about in the sandbox — now behind the endpoint your live integrations actually call. v1 keeps running exactly as it always has, with no deadline attached to it. Nothing you have deployed today needs to change.

What does change is which one I'd point a new integration at, and it's not the same answer for both platforms.

MT4: v2 is the one to build against

The gap has only gotten wider since the sandbox announcement. v2 now covers 147 MT4 endpoints against 42 on v1. Configuration reads and writes, server administration, backups, plugin management, batch snapshots: all of it is v1 never had a surface for.

If you're starting an MT4 integration today, start on v2. /docs/webapi now leads with it. v1 stays fully supported for whoever's already built on it — think of it as the stable, legacy surface, not a deprecated one.

One honest label while I'm at it: v2 itself is still marked Beta on the API — individual endpoint shapes may still move before it's called stable. That's not a reason to wait; it's a reason to pin SDK versions (see below) and expect the occasional changelog entry.

MT5: stay on v1 for now

I'd rather tell you this directly than have the numbers surprise you later. MT5 v2 has 12 endpoints: server time, manager/user/group/symbol reads, paginated positions/orders/deals by group, and partial updates (PATCH) of user, group and symbol records. Dealing, balance operations, account creation and password changes are not on v2 yet. v1 still carries 55 MT5 endpoints, including everything v2 doesn't have.

So the recommendation for MT5 is the mirror image of MT4's: keep building on v1. v2 is there to evaluate — same envelope, same real-time model — but it isn't a replacement yet. When it covers enough to say otherwise, that's its own announcement too.

Correction, 3 October 2026: the first version of this post called MT5 v2 read-only and counted 160 MT4 endpoints against 43. MT5 v2 has included PATCH for user, group and symbol records since 25 June 2026, and the published v2 specification lists 147 MT4 endpoints against 42 on v1 — the figures above are corrected.

The SDKs caught up

All three published SDKs are at 0.2.1 now — TypeScript (@mywebapi.com/sdk on npm), .NET (MyWebApi.Sdk / MyWebApi.Sdk.Models on NuGet), and PowerShell (MyWebApi on the PowerShell Gallery). Open source, MIT-licensed, generated from the same OpenAPI spec the API serves. They still ship OAuth2 token handling, cursor pagination and reconnecting real-time clients behind one client object, exactly as described last time.

One thing hasn't changed: they're all still at 0.x. Minor releases may break compatibility — pin a version.

The Python client remains source-only and is not published to PyPI. If you need it today, build from the repo; I'll announce it here when it ships. Update, 30 September 2026: it has shipped — pip install mywebapi-sdk (PyPI), version 0.3.0.

Where to start

/docs/webapi now walks through the whole path in three steps — set up your Toolbox account and credentials once, then install an SDK and make your first v2 call. Toolbox itself is unchanged: sandbox at pre.toolbox.cplugin.com (free, no SLA, no time limit) and production at toolbox.cplugin.com, billing only once you connect a production platform.