Skip to Content

Orders

Use this category to prepare or manage regular, basket and GTT orders. Managed smart-order flows are also available; check the current smart-order types in the Smart Orders API reference before using a particular smart-order type.

Before building an order, resolve the instrument in the daily Symbol Master and check quantity and price against its lot and tick size. A dry run makes the proposed action visible before a live request.

ActionAPIWhat to check
PlacePOST /api/v3/orders/syncSymbol, side, quantity, order type, product and price fields
ModifyPATCH /api/v3/orders/syncOrder ID and changed fields
CancelDELETE /api/v3/orders/syncOrder ID and the intended cancellation
Basket/api/v3/multi-order/syncEach order in the array; confirm the result for every leg
GTT/api/v3/gtt/orders/syncTrigger, price, quantity and any second OCO leg
Margin estimatePOST /api/v3/multiorder/marginAvailable margin before a live order

Synchronous and asynchronous order endpoints are both available. An asynchronous response is not a final execution result; check the order book or the General WebSocket for status. If a request is submitted without a final acknowledgement, check the order book before sending it again.

For a regular order, side is 1 for buy and -1 for sell. type values are 1 Limit, 2 Market, 3 Stop-Loss Market and 4 Stop-Loss Limit. Use the exact current API fields and product options from the FYERS API documentation when preparing a live payload.

Last updated on