# 1. OAuth Client Credentials → Bearer JWT
TOKEN=$(curl -s -X POST https://auth.cplugin.net/connect/token \
-d 'grant_type=client_credentials&scope=webapi' \
-d "client_id=$CPLUGIN_CLIENT_ID" \
-d "client_secret=$CPLUGIN_CLIENT_SECRET" \
| jq -r .access_token)
# 2. List your trade platforms
curl -H "Authorization: Bearer $TOKEN" \
https://cloud.mywebapi.com/api/TradePlatforms
# 3. Ping one of them
curl -H "Authorization: Bearer $TOKEN" \
https://cloud.mywebapi.com/api/TradePlatforms/$ID/PingTwo API versions, one reference each
Full MT4 / MT5 ManagerAPI surface — Organizations, TradePlatforms, MT4ManagerAPI, MT5ManagerAPI. Both versions run side by side on the same hosts, with the same token; the same references apply to Production and Sandbox.
API v1
stableThe complete surface most integrations run on today. Paths /api/MT4/…, /api/MT5/…, hubs /hubs/mt4/v1, /hubs/mt5/v1.
API v2
betaVersion in the path, faster JSON, SDKs for TypeScript, .NET, PowerShell and Python. Paths /api/v2/…, hubs /hubs/mt4/v2, /hubs/mt5/v2.
Guides — authentication, timeouts, idempotency, realtime: cplugin.com/docs/webapi ↗ · What is new in v2
Swagger UI remains available, deprecated and slated for removal. · Test methods (no auth) ↗
Meet the v2 API
A faster, cleaner endpoint surface is live for testing. v2 puts the version in the path — call
/api/v2/…
directly, no query string — and serves responses through a zero-reflection JSON pipeline. v1 stays
stable and fully supported; migrate at your own pace.
Call /api/v2/… directly — no api-version query parameter to remember.
Source-generated serialization, zero runtime reflection — lower latency and allocations per response.
Hub /hubs/mt4/v2 streams ticks, margins and trade events.
import { CPluginWebApiClient } from '@mywebapi.com/sdk';
const client = new CPluginWebApiClient({
env: 'prod', // or 'staging' for the Sandbox
clientId: process.env.CPLUGIN_WEBAPI_CLIENT_ID,
clientSecret: process.env.CPLUGIN_WEBAPI_CLIENT_SECRET,
});
const time = await client.mt4.getServerTime(tradePlatformId);using CPlugin.SaaSWebApi.Client;
using var client = new CPluginWebApiClient(CPluginEnvironment.Prod, clientId, clientSecret);
var mt4 = client.MT4(tradePlatformId);
var time = await mt4.ServerTimeAsync();$session = Connect-MyWebApi -Environment Production `
-ClientId $env:CPLUGIN_WEBAPI_CLIENT_ID -ClientSecret $secret
Get-MT4ServerTime -Connection $session -TradePlatform $tradePlatformIdfrom cplugin_webapi_sdk import CPluginWebApiClient
with CPluginWebApiClient(env="prod", client_id=client_id, client_secret=client_secret) as client:
time = client.mt4.get_server_time(trade_platform_id)Two environments, one API
Same surface, same OAuth flow, just different hosts. Sandbox is fully separated — no billing, no SLA, safe to break.
- REST cloud.mywebapi.com
- Auth auth.cplugin.net
- Hub /hubs/mt4/v1 · /hubs/mt4/v2 (mt5 alike)
- Manage toolbox.cplugin.com
Multi-region cloud (m3 / m4 / m9), DNS traffic manager routes to the nearest instance. Your pricing in Toolbox ↗
- REST pre.mywebapi.com
- Auth pre.auth.cplugin.net
- Hub /hubs/mt4/v1 · /hubs/mt4/v2 (mt5 alike)
- Manage pre.toolbox.cplugin.com
Fully separated environment with its own Toolbox for client and MT4 / MT5 connection management. No charges, no SLA, may be reset without notice. Use for integration testing before pointing at Production.
Realtime over SignalR
Hubs /hubs/mt4/v1, /hubs/mt5/v1 for API v1 and /hubs/mt4/v2, /hubs/mt5/v2 for API v2. Subscribe to ticks, margins, trade events. WebSockets / Long Polling / SSE — same code path. Auto-reconnect, bearer auth, typed contracts.
Working examples
Full source for download. Plug in your credentials, run, ship.