MyWebApi v2 in open beta, with official SDKs
MyWebApi's v2 API adds a single {data, error, meta} response envelope, real-time over SignalR, and three open-source SDKs that handle OAuth2, pagination and reconnection for you. It runs on the sandbox only for now, and MT5 coverage is still thin — if your integration is MT5, stay on v1.
There are two things to know about MyWebApi's v2 API, and the second one matters more than the first if you run MT5.
Where it runs. v2 is deployed to the sandbox only — it answers on pre.mywebapi.com, while production still serves v1 and nothing else. Client credentials for it are created in the sandbox Toolbox under WebAPI → Clients, and the SDKs reach it through their staging environment setting. So v2 is something to build and evaluate against today, not somewhere to move a live integration.
What it covers. For MT4, v2 is a real expansion: 147 endpoints against 42 in v1, including configuration and management surfaces v1 never exposed. For MT5 it is not there yet — 12 endpoints, all read-only (server time, user, group and symbol lookups, positions, orders and deals by group), against 54 in v1. 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 attached to any of this.
The SDKs are open source and cover the whole v2 surface as it stands — @mywebapi.com/sdk on npm, MyWebApi.Sdk on NuGet, MyWebApi in the PowerShell Gallery. Each one acquires, caches and refreshes OAuth2 tokens for you, streams real-time over the same client and has cursor pagination built in. They target v2 only, and they are at 0.x, so pin a version.
Read the full write-up, numbers included: MyWebApi v2 is in open beta on the sandbox, and there are SDKs for it
This note sums up an article on the CPlugin™ blog. Read the full article ↗