PLACE COVER ORDER

This API enables placement of Cover Orders for authorized end users through a middleware-based integration.

A Cover Order consists of a primary order (Market Order) along with a mandatory Stop Loss order for risk management.

🔍 Query Parameters

Parameter	Type	Required	Description	Example
userId	string	Yes	User ID (UCC)	"{{user_id}}"

🔑 Header Parameters

Header	Type	Description	Example
Content-Type	string	Request payload format	application/json
Authorization	string	Access token for authenticated requests	{{access_token}}
x-api-key	string	API key used to authorize request	{{x-api-key}}

📦Request Body Schema: application/json

Fields	Type	Required	Description	Example/ENUM
Scrip_info	object	Yes	Exchange segments	NSE_EQ
transactional_type	string	Yes	Whether its a BUY or SELL order	BUY
main_leg	object	Yes	Details of the primary order.	See below table
stoploss_leg	object	Yes	Details of the stop-loss (can include multiple legs)	See below table
order_identifier	string	No	Optional Identifier for users own tracking (max 10 Chars)	"Myorder1"
part_code	string	No	Custodian participant code  if any	"P123"
algo_id	string	No	Algo ID for automated strategies	"A001"
strategy_id	string	No	Strategy ID	"S001"
vendor_code	string	No	In-house vendor code	"V123"

📝Scrip Info Object Fields

Fields	Type	Required	Description	Example/ENUM
exchange	string	Yes	Exchange segment	NSE_EQ
scrip_token	integer	No	Unique scrip token (required if symbol-based data is not give)	10100001
symbol	string	No	Scrip symbol	RELIANCE 
series	string	No	Series for equities	EQ
expiry_date	string	No	Expiry date for F&O (yyyy-mm-dd format)	2025-06-27
strike_price	number	No	Strike price for options (in paise)	25000
option_type	string	No	Option type- "CE" (Call) or "PE"(Put)	CE

📝Main Leg Object Fields

Fields	Type	Required	Description	Example/ENUM
order_type	String	Yes	Order Types. Allowed values: RL (Regular Limit) or RL-MKT (Regular Market)	RL/RL-MKT
quantity	integer	Yes	Quantity to transact	100
price	number	Yes	Price for the order. Must be 0 for RL-MKT type.	0

📝Stoploss Leg Object Fields

Fields	Type	Required	Description	Example/ENUM
Legs	Array	Yes	Array of stop loss order legs	See below table

📝Array of objects fields

Fields	Type	Required	Description	Example/Enum
quantity	integer	No	Quantity of SL leg (currently ignored by system).	100
price	number	Conditional	Price at which SL should execute (used only for "SL" type)	1478.00
trigger_price	number	Yes	Price at which stop-loss should trigger and place the order	1480.50

🟢 Success Response - 200 OK

Content-Type: application/json

Field	Type	Description	Example
status	string	Status of API call	"success"
code	string	Response code	"s-101"
message	string	Order placement success message	"Cover order placed successfully"
data	object	Order response details	Refer Data Object Fields

📦 Data Object Fields

Field	Type	Description	Example
orderId	string	System-generated order identification number	"25062900012345"

📝 Notes

• A Cover Order consists of:
  • One primary market order.
  • One mandatory stop loss order.
• trigger_price is mandatory for the stop loss leg.
• Supports Equity, Derivatives, Currency, and Commodity segments where Cover Orders are permitted.
• order_identifier can be used to map and track orders from external systems