Order Placement Guide

Sync APIs (/sync)

All existing /sync order endpoints (single order, multi order, multi-leg order and related /sync flows documented under Sync Order Placement) remain unchanged in request shape and response shape. They continue to return the exchange order reference id (and other fields). Execution is subject to a 10 orders per second (OPS) limit.

Async APIs (/async)

Async counterparts use the same request bodies and HTTP methods as sync where applicable, but target:

• POST https://<host>/api/v3/orders/async — place order (intraday / margin / CNC, same attributes as sync).
• PATCH https://<host>/api/v3/orders/async — modify order (same body rules as sync; id in the body is the order reference once known).
• DELETE https://<host>/api/v3/orders/async — cancel order (JSON body with id, same idea as sync).

Note: stopLoss and takeProfit are not supported with Async Order Placement.

Queuing: When you call an async endpoint, the request is accepted and queued immediately. A queuing mechanism drains the queue and sends work downstream at most 10 orders per second (aligned with the OPS limit). High burst traffic is absorbed in the queue rather than failing fast for rate at the HTTP edge. Final placement, modification or cancellation outcomes are not implied by an HTTP 200 alone.

Immediate HTTP response: On success, the async API returns id_fyers (the FYERS system identifier for the queued/async operation). It does not return id (exchange order number) in this immediate response. Use id_fyers to correlate with:

• General WebSocket — subscribe to order updates; payloads include identifiers such as id and id_fyers (see General WebSocket Overview).
• GET APIs — for example the order book GET /api/v3/orders and related transaction GET APIs (see Order Book).

Hosts: The examples use https://api-t1.fyers.in; other environments may use the same path suffixes on a different host (for example https://api-y1.fyers.in). Set <host> accordingly.

Reference collection: Parity with the internal Postman collection Async apiv3 orders (place/modify/cancel).

Limit Order

• type: 1
• A limit order allows you to buy or sell an asset at a specific price (limitPrice) or better. It will only be executed at the specified price or lower for a buy order, and at the specified price or higher for a sell order.

Sample input:

{
  "symbol": "NSE:SBIN-EQ",
  "qty": 100,
  "type": 1,
  "side": 1,
  "productType": "INTRADAY",
  "limitPrice": 100,
  "stopPrice": 0,
  "validity": "DAY",
  "stopLoss": 0,
  "takeProfit": 0,
  "offlineOrder": false,
  "disclosedQty": 0,
  "isSliceOrder" : false
}

Market Order (MPP)

• type: 2 (MPP: Market Price Protection )
• A market order allows you to buy or sell an asset at the current market price. The limitPrice and stopPrice should be set to 0, as they are not used in this order type.

Sample input:

{
  "symbol": "NSE:SBIN-EQ",
  "qty": 100,
  "type": 2,
  "side": 1,
  "productType": "INTRADAY",
  "limitPrice": 0,
  "stopPrice": 0,
  "validity": "DAY",
  "stopLoss": 0,
  "takeProfit": 0,
  "offlineOrder": false,
  "disclosedQty": 0,
  "isSliceOrder" : false
}

Stop Order / SL-M (MPP)

• type: 3
• A stop order is designed to limit losses on a position. It becomes a market order (MPP: Market Price Protection ) when the stopPrice is reached. The stopPrice is the trigger price at which the market order will be placed.
• The stopPrice must not be higher than the Last Traded Price (ltp) for a sell order and not lower than the ltp for a buy order.

Sample input:

{
  "symbol": "NSE:SBIN-EQ",
  "qty": 100,
  "type": 3,
  "side": 1,
  "productType": "INTRADAY",
  "limitPrice": 0,
  "stopPrice": 100,
  "validity": "DAY",
  "stopLoss": 0,
  "takeProfit": 0,
  "offlineOrder": false,
  "disclosedQty": 0,
  "isSliceOrder" : false
}

Stop Limit Order / SL-L

• type: 4
• A stop-limit order combines features of a stop order and a limit order. It triggers a limit order once the stopPrice is reached.
• The stopPrice must not be higher than the Last Traded Price (ltp) for a sell order and not lower than the ltp for a buy order.
• The stopPrice must be lower than the limitPrice for a buy order and higher than the limitPrice for a sell order.

Sample input:

{
  "symbol": "NSE:SBIN-EQ",
  "qty": 100,
  "type": 4,
  "side": 1,
  "productType": "INTRADAY",
  "limitPrice": 100,
  "stopPrice": 95,
  "validity": "DAY",
  "stopLoss": 0,
  "takeProfit": 0,
  "offlineOrder": false,
  "disclosedQty": 0,
  "isSliceOrder" : false
}

Creating TPSL

From order placement (new order)

Use the Orders API Single Order and send the takeProfit and stopLoss parameters with the order, using an applicable supported productType (INTRADAY, CNC, MARGIN or MTF). TPSL is supported only with sync order placement; async order placement does not support takeProfit and stopLoss.

From open position

Use the Positions API Set Stop Loss & Target. Send the positionId with takeProfit and/or stopLoss. qty is optional and can’t be more than the position quantity.

Modifying TPSL

From order placement (new order)

While the parent order is pending (not yet executed), use the Orders API Modify Single Order and send the new takeProfit and/or stopLoss values.

From open position

Once the parent order has executed and you have an open position, use the Positions API Modify Stop Loss & Target. Send only the parameters you want to change; any parameter you leave out keeps its current value.

Cancelling TPSL

From order placement (new order)

If a pending parent order is cancelled using the Orders API Cancel Single Order, its linked Take Profit and Stop Loss orders are cancelled automatically.

To cancel only the linked Take Profit or Stop Loss without cancelling the parent order, use the Orders API Modify Single Order and pass null for the applicable takeProfit or stopLoss parameter. Pass both parameters as null to cancel both.

From open position

Use the Positions API Cancel Stop Loss & Target and pass null for the parameter you want to cancel: takeProfit, stopLoss, or both.