Place Order - Any Scrip

This API allows you to place a fresh buy or sell order for any available scrip . Users can specify the type of order, the quantity, and other parameters to execute their trading orders.

🔑Header Parameters

Header	Type	Required	Description	Example
content_type	String	Yes	MIME type of the request	application/json
authorization	String	Yes	Bearer token for user authentication	Bearer {access_token}
x-api-key	String	Yes	API Key provided	{x-api-key}

📦Request Body Schema

Field	Types	Required	Description	Example/ENUM
scrip_info	Object	Yes	Provide either (exchange + token) or detailed scrip fields	{exchange: NSE, token: 12345}
transaction_type	String	Yes	BUY or SELL	BUY/SELL
product_type	String	Yes	Product type based on product strategy	INTRADAY , DELIVERY
order_type	String	Yes	Type of Order	"RL-MKT, LIMIT,SL-MKT"
quantity	integer	Yes	Indicates the total quantity for which the order should be placed.	100
price	number	Conditional	Default: 0 The price at which the order will be placed, specified in rupees.	250.50
trigger_price	number	Conditional	Trigger price for the order, applicable only for Stop Loss Limit (SL) and Stop Loss Market orders (SL-MKT).	245.00
disclosed_quantity	integer	No	Disclosed quantity refers to the portion of the total order quantity that is visible in the market.	20
validity	string	No	Default: "DAY" The Order Validity value will be dependent on exchange segments in which the order is being placed.	"DAY"
validity_days	integer	Conditional	Number of days for which the GTD order needs to be carried forward.	7
is_amo	boolean	No	Default: falseIndicates whether the order is an AMO (After Market Order). AMO orders are stored in the system and submitted to the exchange on the next trading day.	true or false
order_identifier	string	No	<=10 characters An optional field to apply to an order to track it.	ORDER123
part_code	string	No	Participant Code of the Custodian	Part001
algo_id	string	No	Algo id for strategy generated orders	ALGO123
strategy_id	string	No	Strategy id for strategy generated orders	STRAT456
vender_code	string	No	Vender code for inhouse application	VEND001

📝Scrip Info Object Fields

Field	Type	Description	Example/ENUM
exchange	String	Exchange segments to which the order is to be sent	"NSE_EQ"
scrip_token	integer	Exchange assigned identification number for the scrip or instrument	10243
symbol	string	Symbol code as per the exchange's scrip master file	INFY
series	string	Series applicable to equity instruments	EQ
expiry_date	string	Expiry date of the contract in yyyy-mm-dd format, applicable for futures and options.	2025-10-31
strike_price	number	Strike price of the contract (usually in paise), applicable for options	160000
option_type	string	Indicates the option type: CE for Call Option and PE for Put Option	"CE", "PE"

🟢Success Response - 200 OK

Content-Type: application/json

Field	Type	Description	Example/ENUM
Status	String	Indicates the result of API Call	"success"
Code	String	Response code corresponding to the request	"s101"
Message	String	Descriptive message for the response	"order entry sent to OMS"
Data	Object	Contains the order information	See below

📘Data Object Info field

Fields	Type	Description	Example/ENUM
orderId	string	System generated order ID	"NWSYF00005>3"

OMS Acknowledgement ≠ Exchange Confirmation

A response such as "Order Entry Sent to OMS", "Order Modification Sent to OMS", or "Order Cancellation Sent to OMS" only indicates that the request has been accepted by the OMS.

It does not mean that the order has been accepted, modified, or cancelled at the exchange.

📡 To receive actual exchange-level status updates and confirmations, subscribe to the Message Socket (Streaming API) and monitor real-time order responses.