Account
The account's login, status and connection, and the balance, equity and margin from its terminal's last report (once a second). Read from the engine, not the terminal, so it answers while the terminal is away.
Path
The account's id, acc_ and 26 characters, as the dashboard shows it.
Response
The account's id.
The MT5 login.
The broker's trade server.
What the engine knows of the account's terminal: starting, connected, disconnected, unreachable (the broker's server can't be reached; it keeps trying), stopped, or a status someone has to act on: auth_failed (the broker refused the login), server_not_found, login_unknown or refused.
Whether the terminal reports a connection to the trade server.
Whether MT5 lets this terminal trade: the terminal, the account and automated trading all allow it. False for an investor (read-only) login.
The broker.
The account's currency.
hedging, netting or exchange.
demo, contest or real.
The trade server's time at the last report: broker server time, seconds since 1970.
Whether the account's kill switch is engaged.
Fields of kill_switch
When it was engaged: seconds since 1970 (UTC). Null when it is not engaged.
The deviation, in points, its closing deals carry. Null when it is not engaged.
Errors
| 401 | invalid_api_key | The key is not a workspace's current key (a rolled key stops working within about a minute). |
| 401 | missing_api_key | No API key: send it as |
| 404 | no_such_account | No such account, or one the key's workspace doesn't have: the two look the same. |
| 503 | engine_busy | The account's engine host has too many calls in flight (256). Nothing was done; try again. |
| 503 | engine_unavailable | The account's engine host is not connected to Pipsocket, or disconnected while the call waited. A trade it already had is still settled: look it up. |
| 504 | engine_timeout | The account's engine did not answer within 30 seconds. |