Order types and controls
Choose an order type, review its risk and follow execution through to the account.
Choose the order type
The current ticket supports Market and Limit. Time-in-force is derived from the type; there is no separate time-in-force selector.
| Type | Execution rule | Unfilled quantity |
|---|---|---|
| Market | Attempts immediate execution within the venue’s protective price band. | Cancels immediately: IOC, or immediate-or-cancel. |
| Limit | Executes at your limit price or better. It can execute immediately if it crosses the book. | Can rest until filled or cancelled: GTC, or good-till-cancelled. |
Enter direction, price, and size
Choose Buy / Long or Sell / Short. Against an existing position, an opposite-side order can reduce exposure; without Reduce Only, sufficient size can also reverse it. Check Current Position before submission.
For Limit, enter the maximum price you will pay to buy or the minimum price you will accept to sell. For Market, Reference is a current reference value, not a fixed execution price.
Enter Size and inspect the unit selector. Base units describe the underlying quantity; quote sizing describes value. The percentage control derives a draft allocation from available account inputs and leverage. It is not a promise that the order can use exactly that fraction of the account. Use the fresh preview to review estimated execution and margin; the venue checks the order again at submission.
How ticket fields become an order request
The terminal converts the draft into the request variant supported by the current market. Amounts must preserve exact decimal precision, and optional controls must be valid for the selected order type. Preview and placement use different amount formats: preview uses integer atoms, while placement quantities and prices use decimal strings. Use the schema for the operation you are calling.
A placement starts with clientOrderId and the request’s Idempotency-Key. There is no server orderId in this initial body. The server returns that identity for later reads and cancellations. The Orders API includes the complete placement example and request variants.
| Ticket or client input | Placement field | Interpretation |
|---|---|---|
| Selected account and market | accountId, marketId | Use the bound account and the exact current catalogue identifier. |
| Market or Limit | orderType | market uses IOC; limit uses GTC. Public placement has no timeInForce field. |
| Buy / Long or Sell / Short | side | buy or sell; the effect also depends on existing exposure. |
| Size in base units | quantity | An exact decimal string. Both market and limit quantity variants support it. |
| Market size in quote value | notional | The alternative market-order variant; do not send quantity and notional together. |
| Limit price | price | An exact decimal string on the limit-order variant. |
| Selected leverage | leverageX | An optional positive integer, constrained by the current market and risk preview. |
| Reduce Only | reduceOnly | Restricts execution to reducing eligible existing exposure. |
| Post Only | postOnly | Limit-only maker intent; it must not take liquidity immediately. |
| Take Profit / Stop Loss | autoClose | Uses takeProfitPriceAtoms and/or stopLossPriceAtoms, converted with the market’s price scale. |
| Logical order identity | clientOrderId | Created before submission and retained across retries of that same instruction. |
Review a fresh order preview
Wait for the preview after editing the ticket. It estimates entry, slippage, required margin, fees, and liquidation price from current market and account inputs. Editing size, side, price, leverage, or options can require a new preview. Account changes and expiry can also invalidate it.
If margin is insufficient or estimated execution exceeds the slippage safety band, the ticket blocks submission and explains why. Adjust the draft or wait for data to recover. A missing liquidation estimate is not a statement that liquidation cannot occur.
A successful preview does not place an order or reserve its estimates. Prices and available liquidity can change before execution.
Order validation and precision
Order validation and precision
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
The terminal preserves exact decimal amounts when preparing an order. The service preview calculates margin, fees and risk against the current draft and account state. A usable preview must match those inputs and be less than 15 seconds old.
Exact amounts. Values with unsupported decimal precision are rejected instead of silently rounded. Check the selected size unit and market precision before submission.
Current risk. The service evaluates margin, fees, liquidation, slippage and sufficiency. Submission also requires fresh account data, live selected-market data and satisfied risk controls. A preview does not reserve liquidity or guarantee an execution price.
Refresh when needed. Editing the draft can obtain a new preview. If account conditions change or the preview expires, review the updated state and use the available refresh action before submitting.
One instruction, one identity. Placement uses clientOrderId plus Idempotency-Key. The venue returns orderId after submission. If the outcome is unknown, retain the original account-bound instruction while checking its result.
See the Orders API for exact request fields.
Follow the lifecycle
Submit once, then read the ticket status. Pending means a result is still being obtained. Accepted means the request was accepted for processing; check whether it is open, partially filled, filled, or cancelled. Rejected and failed messages require reading the specific reason before another attempt.
Check Open Orders for remaining quantity and Fills for executions and actual fees. A partially filled market order can finish cancelled with some exposure already created. A partially filled limit order can leave a resting remainder.
If the outcome is unknown, use Check status. Do not assume a timeout means rejection. Keep the original request and use the application’s exact-retry action only after its status checks. See troubleshooting.
Use Reduce Only to avoid increasing exposure
Reduce Only restricts the order to shrinking an existing position. It cannot increase the position or flip it to the opposite side. Select the direction opposite your existing exposure and review the current position size.
A reduce-only order can be refused or cancelled if there is no eligible position left to reduce. Other fills or a previous close may have changed that position while the draft was open. Refresh the account before creating another close request.
Enabling Reduce Only clears attached TP and SL prices and disables Take Profit / Stop Loss in the ticket. See positions and closing.
Use Post Only for maker-only limit orders
Post Only is available for Limit orders. It permits the order to enter the book only when it would not immediately match. If your price crosses the opposite side, the order does not execute as a taker simply to satisfy the requested size; inspect the returned result.
An ordinary limit order can take liquidity immediately, so choosing Limit alone does not establish a maker fee. Actual fill role and fees appear in Fills. Post-only limit orders use GTC.
See funding and fees for the difference between execution fees and position funding.
Adjust leverage within the market limit
Select the leverage control to open Adjust Leverage. Choose a value within the current market limit, then review the updated order preview. Maximum leverage and margin tiers come from live market metadata; they are not the same for every contract.
Higher leverage increases sensitivity to price moves relative to the margin committed and can reduce the size permitted by risk checks. The selected value is an input to this order. It is not a global account credit or proof that an existing position’s margin mode changed.
Read margin and liquidation before using leverage.
Cancel a resting order
Open Trade → Open Orders, find the order, and select Cancel. Cancellation applies to the unfilled remainder. It cannot undo fills that occurred before cancellation was accepted. Fees already charged for those fills remain. Edel does not charge a placement fee.
Wait for confirmation. Cancelled · Syncing means cancellation was confirmed while account views are catching up. An unknown result requires a status check; a missing row alone does not prove cancellation. The order may instead have filled.
Cancellation can remain available while a market is paused, reduce-only, cancel-only, or session-restricted, but a global halt can block it. The current terminal does not provide an in-place amend flow. To replace a resting order, first establish the cancellation result, then review a new order and its fresh preview.
Attach TP and SL in the order ticket
Prepare a Market or Limit order and enable Take Profit / Stop Loss. Enter a TP Price, an SL Price, or both. At least one price is required when the option is enabled. The prices use the selected market’s quote unit and permitted precision.
These conditions are submitted with the opening order. A checked box or completed draft is not evidence that protection is active: first confirm the order’s accepted result and resulting position.
The current ticket does not offer these attached conditions on a Reduce Only order. Enabling Reduce Only clears both values.
Put each condition on the correct side
The ticket validates the prices against the entry or reference price for the draft. Changing side or entry price can invalidate previously entered conditions. Review them after every change.
| Direction | Take profit | Stop loss |
|---|---|---|
| Buy / Long | Above the entry/reference price | Below the entry/reference price |
| Sell / Short | Below the entry/reference price | Above the entry/reference price |
Understand the paired behavior
When TP and SL are attached together, they form an OCO pair: one cancels the other. The first condition to fire cancels its sibling. This prevents treating both conditions as independent exits that will necessarily execute.
The trigger price is a condition for an exit, not a guarantee of execution at that exact price. Liquidity, price movement, market restrictions, and the current position can affect the result. The visible chart can use a different price series from account risk values; do not infer an execution solely from a chart crossing.
For a confirmed exit, inspect Fills and the remaining position. A stop loss should not be treated as protection against every loss or liquidation.
Monitor the resulting position
After entry, keep position size, mark price, margin status, and fills under review. If the order was rejected, partly filled, or has an unknown outcome, establish the actual exposure before placing another exit.
Do not submit another opening order merely to change an attached TP or SL. The ticket attaches TP and SL when placing an order; it does not currently provide a dedicated editor for an existing position’s conditions. If the displayed result is unclear, use Support. To reduce an active position yourself, follow positions and closing.