Call ConnectEx with the account's login, password and trade-server name. If the account has no live session, the service signs it in and only answers once the account is connected to the broker's trade server. It waits up to about two minutes for that, and longer in total if other accounts are being started at the same moment, because starts are queued. If the session is already live and you send the same password, the call returns almost immediately and nothing is restarted. On success the body is the account id as plain text (acct-<login>), which you pass as ?id= on every other /v1 call. On failure the body is JSON { "code", "message" } with the HTTP status set by errorReplyStatusCode (405 unless you choose another), so branch on code, not on the status.

Returns { "code": "OK" } when the account behind ?id= has a live session, and { "code": "INVALID_TOKEN", "message": "token not found or expired" } when it does not. Both answers come back as HTTP 200, so read the code field. Use it to check a stored id before you reuse it. On INVALID_TOKEN, call ConnectEx again with the password and server. Despite its name, this call does not connect anything.

Returns { "code": "OK", "terminalInstanceGuid": "acct-<login>" } when the account behind ?id= has a live session. When it has none, it returns HTTP 405 with { "code": "NOT_CONNECTED", "message" }. Despite its name, this call never starts, restarts or reconnects a session. Use ConnectEx for that. terminalInstanceGuid is the same acct-<login> account id that ConnectEx returns.

Returns HTTP 200 with the plain-text body ok when the account behind ?id= has an active session, and HTTP 403 with an empty body when it does not. It reads no account data and makes no round trip to the broker, so it answers immediately and is safe to call often. It tells you whether the session exists, not whether the account can trade right now, so use a data call such as AccountSummary when you need to confirm that. When you get 403, start a session with ConnectEx.

GET /v1/Disconnect always returns { "code": "OK" } and has no effect. The session keeps running, its positions stay open, and the same id keeps working. It exists so that clients which call Disconnect at the end of a flow keep working. To actually stop a session, call POST /orchestrator/disconnect, which needs the Bearer token described under Authentication, or have it stop automatically with ConnectEx's idleHours.

Returns { "code": "OK" } for any request that carries a valid ApiKey header. It uses no account, so it is the simplest way to confirm connectivity and your key before you start a session. A missing or invalid key returns 401.

Reads the account's current figures from its live session. All money values are in the account currency, given in currency. Some fields appear under two names for client compatibility: company and accountCompanyName both hold the broker's company name, and server and accountServer both hold the trade-server name. The account needs a live session; without one the call returns 502.

Returns { "serverTimeZone": 0, "serverTimeZoneInMinutes": 0, "utcOffsetMinutes": 0 } on every request. The values are fixed and are not read from the broker or the account. No id is needed, and one is ignored if sent. The endpoint exists so that clients which look up a server time-zone offset during start-up keep working.

Returns the latest bid, ask and last price the broker has published for one symbol on a connected account. You can send a base name such as EURUSD or XAUUSD, and it is mapped to this broker's exact symbol name for you (see Symbol names). If no price has arrived yet for the symbol, which is typical the first time a symbol is requested in a session, the API waits briefly and retries once before it answers. The response holds prices only. It has no timestamp, spread or symbol name, so work out the spread as ask - bid and use TickHistory when you need timestamped prices. Quoting a symbol also adds it to the account's active (Market Watch) set, which matters for Symbols on very large brokers.

Returns a flat JSON array with the name of every symbol the broker makes available to this account. Each name is spelled exactly as the broker spells it, including any suffix such as ".s". Use it to build a symbol picker, or to find a broker's exact spelling before calling GetQuote, PriceHistoryEx or OrderSendTask. The list covers every symbol the broker offers, not only the account's active ones. On some brokers it runs to many thousands of entries. Fetch it once per account and cache it.

Returns an object whose keys are exact broker symbol names and whose values are each symbol's trading specification. That covers price precision (digits, point, tick size), the base, profit and margin currencies, whether and how the symbol can be traded (tradeMode), and the minimum, maximum and step for order volume. Use it to round prices to the symbol's tick size, and lot sizes to volumeStep, before calling OrderSendTask. On brokers that list more than 4,000 symbols, only the account's active (Market Watch) symbols are included so the call stays responsive. Any symbol you have quoted, charted or traded through the API becomes active, so if one is missing, call GetQuote for it and then fetch Symbols again. The response can be large, so cache it per account.

Returns up to 5,000 of the most recent OHLC bars for one symbol, which is the data behind a price chart. You give the timeframe in minutes, and it is snapped to the nearest standard MT5 timeframe: 1, 5, 15, 30, 60, 240, 1440, 10080 or 43200 minutes, that is M1 to MN1. Bars are ordered oldest to newest, and the window always ends at the current bar. While the market is open, that last bar is still forming, so its high, low and close keep moving until it closes. You cannot ask for a specific date range; to see further back, request more bars or a longer timeframe. Bar times are in the broker's server time and have no time-zone suffix.

Returns the individual price updates (ticks) for one symbol between from and to. Each tick has bid, ask, last, volume and a time to the millisecond. That is finer than any bar timeframe, which makes ticks useful for spread analysis, back-testing or replaying price action. By default the window is the 15 minutes ending at to, and to defaults to now. A window can be at most 6 hours long: a longer request is cut to the 6 hours ending at to, and the response sets truncated: true. To cover a longer period, page backwards. The response also returns the window actually used (in epoch seconds) and the broker's exact symbol name.

Use this to see everything currently live on the account: filled positions with their floating profit, and pending (limit/stop) orders that have not triggered yet. Positions come back in positionInfos and pending orders in openedOrders. Both arrays are empty, not missing, when there is nothing open. Several fields are deliberately duplicated under two names (for example lots/volume, openPrice/priceOpen, stopLoss/sl, expertId/magic) so you can read whichever naming your client prefers; the values are identical. Call this to reconcile state after a trade call came back with error.errorCode TIMEOUT: the outcome of that request is unknown, so check here whether the order or position exists before you retry. NOT_CONNECTED usually means nothing was sent, but if the connection dropped while the request was in flight the outcome is unknown as well, so checking here is the safe move.

Set operation to Buy or Sell for a market order, which is filled at the current ask (Buy) or bid (Sell); any price you pass is ignored for market orders. Set it to a pending type (BuyLimit, SellLimit, BuyStop, SellStop, BuyStopLimit, SellStopLimit) to place a working order, which then requires a positive price. Every trade outcome, including a broker rejection, comes back as HTTP 200, so branch on the body's code field ("OK" or "ERROR"); only a missing or invalid id (400) or a bad API key (401) changes the HTTP status. Pass a clientOrderId to make retries safe: a repeat of the same id within 5 minutes returns the first result instead of opening a second position. If you get errorCode TIMEOUT or NOT_CONNECTED, the order may or may not be live; check OpenedOrders before sending again.

Pass the ticket of an open position or a working pending order. For a position, only stoploss and takeprofit can change. For a pending order, price, stoploss, takeprofit and stoplimit can change, and its expiration and time-in-force are kept. A field you omit keeps its current value, and sending 0 clears a stop-loss or take-profit. Trade outcomes, including rejections, timeouts and a disconnected account, return HTTP 200 with body.code "OK" or "ERROR". Only a missing or invalid id (400) or a bad ApiKey (401) uses a non-200 status.

Pass a position ticket to close it at the current market price: a Buy position closes at the bid and a Sell position at the ask. Add lots to close only part of the position; leave it out to close all of it. If the ticket belongs to a pending order instead of a position, that order is cancelled, so this one endpoint can close or cancel anything that is open. Once the request is authenticated and carries a valid id, the reply is always HTTP 200: body.code is "OK" on success or "ERROR" on failure, and the reason is in body.error.errorCode.

Use this to remove a limit, stop or stop-limit order that has not triggered yet. It only accepts tickets of pending orders that are still working. To close an open position, use OrderCloseTask. If the order has already triggered, expired or been cancelled, it is no longer a working pending order and the call fails with error.errorCode "-8". The HTTP status is 200 whether the cancel succeeds or fails, so check body.code: "OK" means the order was removed, and "ERROR" means it was not.

On a hedging account you can hold a Buy and a Sell on the same symbol at the same time. Close By settles one against the other in a single trade operation instead of closing each separately. Pass the position to close as ticket and the opposite position as closeByTicket (or its alias ticketBy). The call always answers HTTP 200 once the account id is valid, with body.code "OK" on success or "ERROR" on failure. The specific failure reason is in body.error.errorCode.

Returns the account's closed trades within a time window, defaulting to the last 90 days. You get one row per position, newest close first. Each row merges the position's opening and closing deals into one trade, with volume-weighted open and close prices, open and close times, closed volume, and net profit after swap and commission. A trade is in the window when its last closing deal is inside it, so a position opened before from but closed inside the window is included. The response holds at most the 1,000 most recent trades. Use OrderHistoryPagination if a window can hold more than that or you need a different sort order.

Returns the same closed-trade rows as OrderHistory, split into zero-based pages. You choose the page size and whether to sort by close or open time, ascending or descending. There is no 1,000-row cap, so use this endpoint to export a whole window. The response gives the number of pages but no total row count. Each page request rebuilds the window from scratch, so pin both from and to when you need pages that stay consistent while trades are still closing.