FiveSocket API

FiveSocket gives you live MetaTrader 5 account data over a plain REST API. Every read performs a fresh, exclusive MT5 login inside a disposable worker, returns what the terminal reported, and destroys the worker. Nothing is cached, synthesized, or replayed.

How reads work

Every data response carries observation metadata so you always know what you are looking at:

observedAt is the UTC timestamp of the live observation
latencyMs is how long the terminal session took
x-request-id identifies the request for support and audit
responses with account data are always Cache-Control: no-store

Monetary values, prices, and volumes are decimal strings, never floats. Timestamps are UTC ISO 8601 strings.

Endpoints

The V1 surface is deliberately small:

Endpoint	Purpose
`POST /v1/accounts`	Link an MT5 account with a real read-only login check
`GET /v1/accounts`	List linked accounts
`DELETE /v1/accounts/{accountId}`	Disable an account and revoke future reads
`GET /v1/accounts/{accountId}/balance`	Balance, equity, and currency from a fresh login
`GET /v1/accounts/{accountId}/positions`	Currently open positions
`GET /v1/accounts/{accountId}/trades`	Closed deals for a time window, cursor paginated
`GET /v1/accounts/{accountId}/snapshot`	Balance, positions, and recent trades from one session

When you need more than one view of an account, prefer snapshot. It serves everything from a single exclusive login, so you pay the login latency once.

Explore

Quickstart

Link an account and make your first live read.

Authentication

API keys, scopes, and how tenant identity works.

Errors and limits

The error envelope, retry rules, pagination, and idempotency.

Every endpoint's request and response shape lives in the API Reference tab, generated from the OpenAPI specification the gateway itself serves at /v1/openapi.json.