Skip to main content
POST /api/v1/orders/pending places a pending order. It requires the POST:/api/v1/orders/pending scope, a verified account, trading enabled, and Idempotency-Key. A token restricted to /orders/market does not grant this scope.

​
Supported types

For immediate buys/sells (types 0 and 1), use market orders.

​
Request

Prices are illustrative, not current quotes. volume is an integer in MT5 units: 100 equals 0.01 lots. There is no conversion from lots. login, symbol, volume, order_type, and price are required. comment is optional, accepts up to 31 characters, and defaults to REST API. digits is resolved automatically; do not send it. For stop-limit orders, also provide the required stop_limit_price:
Reaching the activation price creates a limit order; it does not imply immediate execution. For buy stop-limit, the limit price must be at or below the activation price; for sell stop-limit, at or above. The other four types reject stop_limit_price. The backend maps price to PriceOrder and stop_limit_price to PriceTrigger.

​
Validation and lifetime

The backend queries effective symbol settings for the account and validates volume minimum, maximum, and step; allowed order type and direction; and price decimals and tick size. It does not round or change the requested volume. Prices must be positive and finite. Additional fields produce 422. This version uses GTC (TypeTime=0) and RETURN (TypeFill=2) and requires GTC support for the symbol. Custom expiration dates, SL, and TP are not exposed. Broker rules may cancel orders; GTC does not guarantee indefinite persistence. MT5 checks margin, sessions, distances, and price placement when processing the order.

​
Submission and tracking

Save the body as pending.json and use a separate key for each intent.
Store answer.id or answer.ID and query the result. The initial response confirms receipt, not placement or execution. Then query GET /api/v1/accounts/{login}/orders for active orders. Use cancel pending order to request cancellation. Order modification is not exposed. Revoking verification does not cancel existing orders. Idempotency also applies here. Do not change keys to repeat a request with an uncertain outcome. A reservation may remain pending after lookup or validation failures before submission.