0% found this document useful (0 votes)
45 views6 pages

API Order Placement Guidelines

The document provides API guidelines for order placement, login mechanisms, and order management processes, including placing, modifying, and canceling orders. It emphasizes the importance of matching parameters with the contract master and outlines specific formats for order requests. Additionally, it includes examples of request and response structures for various operations within the API.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
45 views6 pages

API Order Placement Guidelines

The document provides API guidelines for order placement, login mechanisms, and order management processes, including placing, modifying, and canceling orders. It emphasizes the importance of matching parameters with the contract master and outlines specific formats for order requests. Additionally, it includes examples of request and response structures for various operations within the API.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

API Guidelines

After a thorough analysis of error logs and the identification of common


mistakes within API logs, we are sharing these guidelines to assist those
experiencing errors during request and response processes.

Order Placement

For order placement you need to scrip token number from contract master. You can use the
below link
[Link]

 sample Line
{"exch":"NSE","exchange_segment":"nse_cm","formatted_ins_name":"IDEA-
EQ","group_name":"EQ","instrument_type":"0","lot_size":"1","pdc":null
,"symbol":"IDEA","tick_size":"0.05","token":"14366","trading_symbol":
"IDEA-EQ"}

 When placing order all the parameters should match with the contract master(Symbol
id -token (token":"14366") : Trading Symbol – ("trading_symbol":"IDEA-EQ")
 )
 For NFO contracts there is a change in format. New format is like:
BANKNIFTY28SEP23F
 Old format: BANKNIFTY28SEP23FUT

 Everyday a contract file will updated at 08:00 AM. Before that previous day contract
will be downloaded.
Login Mechanism

Please follow login mechanism mentioned below and don’t use the auth flow from ant
[Link]
Place order
When placing order all the parameters should be passed compulsorily and for normal order

Complexty should be passed regular. For market orders the price should be passed 0.0

[
{
"complexty": "REGULAR",
"discqty": "0",
"exch": "NSE",
"pCode": "MIS",
"prctyp": "L",
"price": "10",
"qty": 1,
"ret": "DAY",
"symbol_id": "14366",
"trading_symbol": "IDEA-EQ",
"transtype": "BUY",
"trigPrice": ""
}
]

Response
[
{
"stat": "Ok",
"NOrdNo": "23092200300907"
}
]
Modify order
Request
{
"discqty":0,
"exch": "NSE",
"filledQuantity":0,
"nestOrderNumber": "23092200300907",
"prctyp": "L",
"price": "10",
"qty": 1,
"trading_symbol": "IDEA-EQ",
"trigPrice": "00.00",
"transtype":"BUY",
"pCode":"MIS"
}

Response
{
"stat": "Ok",
"nestOrderNumber": "23092200300907"
}
Cancel Order
Request
{
"exch": "NSE",
"nestOrderNumber": "23092200300907",
"trading_symbol": "IDEA-EQ"
}

Response
{
"stat": "Ok",
"nestOrderNumber": "23092200300907"
}
Square off position
Exchange must in mcx_fo (eg, mcx_fo,nse_cm nse_fo, bse_fo )
Request Response
[ [

{ {

"exchSeg": "mcx_fo", "stat": "Ok",

"pCode": "MIS", "NOrdNo": "23092200319878"

"netQty": "1", }

"tockenNo": "257629", ]

"symbol": "GOLDPETAL29SEP23"

You might also like