Hello @trader_noob,
Apologies for the inconvenience. Rest assured, we are looking into it and would come up with fixes and usage best practices.
Regards
SmartAPI Team
Hello @trader_noob,
Apologies for the inconvenience. Rest assured, we are looking into it and would come up with fixes and usage best practices.
Regards
SmartAPI Team
Dear SmartAPI Users,
In our quest to provide the best service to our customers, we have added additional rate limits on per minute and per hour basis.
Here are the new rate limits for various endpoints:
Sr. No. | API | Per second | Per Minute | Per Hour |
---|---|---|---|---|
1 | /rest/auth/angelbroking/user/v1/loginByPassword |
1 | NA | NA |
2 | /rest/auth/angelbroking/jwt/v1//generateTokens |
1 | NA | 1000 |
3 | /rest/secure/angelbroking/user/v1/getProfile |
3 | NA | 1000 |
4 | /rest/secure/angelbroking/user/v1/logout |
1 | NA | NA |
5 | /rest/secure/angelbroking/user/v1/getRMS |
2 | NA | NA |
6 | /rest/secure/angelbroking/order/v1/placeOrder |
20 | 500 | 1000 |
7 | /rest/secure/angelbroking/order/v1/modifyOrder |
20 | 500 | 1000 |
8 | /rest/secure/angelbroking/order/v1/cancelOrder |
20 | 500 | 1000 |
9 | /rest/secure/angelbroking/order/v1/getOrderBook |
1 | NA | NA |
10 | /rest/secure/angelbroking/order/v1/getLtpData |
10 | 500 | 5000 |
11 | /rest/secure/angelbroking/order/v1/getPosition |
1 | NA | NA |
12 | /rest/secure/angelbroking/order/v1/getTradeBook |
1 | NA | NA |
13 | /rest/secure/angelbroking/order/v1/convertPosition |
10 | 500 | 5000 |
14 | /rest/secure/angelbroking/order/v1/searchScrip |
1 | NA | NA |
15 | /rest/secure/angelbroking/order/v1//details/{GuiOrderID} |
10 | 500 | 5000 |
16 | /rest/secure/angelbroking/portfolio/v1/getHolding |
1 | NA | NA |
17 | /rest/secure/angelbroking/portfolio/v1/getAllHolding |
1 | NA | NA |
18 | /rest/secure/angelbroking/market/v1/quote |
10 | 500 | 5000 |
19 | /rest/secure/angelbroking/margin/v1/batch |
10 | 500 | 5000 |
20 | /rest/secure/angelbroking/gtt/v1/createRule |
10 | 500 | 5000 |
21 | /rest/secure/angelbroking/gtt/v1/modifyRule |
10 | 500 | 5000 |
22 | /rest/secure/angelbroking/gtt/v1/cancelRule |
10 | 500 | 5000 |
23 | /rest/secure/angelbroking/gtt/v1/ruleDetails |
10 | 500 | 5000 |
24 | /rest/secure/angelbroking/gtt/v1/ruleList |
10 | 500 | 5000 |
25 | /rest/secure/angelbroking/historical/v1/getCandleData |
3 | 180 | 5000 |
We hope that the new rate limits help you to get a better trading experience.
Thank you.
Regards
SmartAPI Team
Hello @robotrade,
We have identified the issue and are working to resolve it. Apologies for the inconvenience.
Thank you.
Regards
SmartAPI Team
Hello @trader_noob, @godboleamit
As @andyvoid has mentioned, it'll help in tracking modified orders. One more use case is fetching Individual Order Status. Earlier a user had to fetch the whole orderbook and check for their orders, now using the Individual Order Status API and Unique Order ID any user can track their orders instantly. Our main focus for introducing this was to provide a faster response time to order status which can be easily done now using the unique order ID parameter.
@gjs thank you for suggesting this feature. We have noted this and will update you once it becomes available.
If you still have any questions, please let us know.
Thank you.
Regards
SmartAPI Team
Hello @godboleamit,
Thank you for this suggestion. We will keep it in mind while implementing new features and enhancements for SmartAPI. Thanks for being an active user and raising this issue for the trading community.
Thank you.
Regards
SmartAPI Team
Hello @perceptron,
Currently there is a limit of 3 connections per client code for Websocket Streaming. There is no additional cap or limit on it.
Thank you.
Regards
SmartAPI Team
Hello @RM ,
We have noted your suggestion and will be conveying it to the requisite team for action. Thank you for being an active SmartAPI user and highlighting issues.
Your feedback helps us make SmartAPI better.
Thank you.
Regards
SmartAPI Team
Dear SmartAPI Users,
We had received feedback from some of you that we should add exchange order ID key in the response of getOrderBook
API. We have heard you and have made the same available now. If you check the response from getOrderBook
API, you will find the exchange order ID as well. We hope that this helps you in your trading journey.
Here is a sample response from getOrderBook
{
"status": true,
"message": "SUCCESS",
"errorcode": "",
"data": [
{
"variety": "NORMAL",
"ordertype": "LIMIT",
"producttype": "DELIVERY",
"duration": "DAY",
"price": 161.7,
"triggerprice": 0.0,
"quantity": "1",
"disclosedquantity": "0",
"squareoff": 0.0,
"stoploss": 0.0,
"trailingstoploss": 0.0,
"tradingsymbol": "IOC-EQ",
"transactiontype": "BUY",
"exchange": "NSE",
"symboltoken": "1624",
"ordertag": "",
"instrumenttype": "",
"strikeprice": -1.0,
"optiontype": "",
"expirydate": "",
"lotsize": "1",
"cancelsize": "0",
"averageprice": 161.7,
"filledshares": "1",
"unfilledshares": "0",
"orderid": "240516000001760",
"text": "",
"status": "complete",
"orderstatus": "complete",
"updatetime": "16-May-2024 11:18:11",
"exchtime": "16-May-2024 09:00:06",
"exchorderupdatetime": "16-May-2024 11:18:11",
"fillid": "",
"filltime": "",
"parentorderid": "",
"uniqueorderid": "ade58561-4464-416c-9903-e509aa5d5e1e",
"exchangeorderid": "1100000000048358"
}]
}
Regards
SmartAPI Team
Hello @don,
This API does not provide Open Interest info for now. Rest assured, we have taken this into consideration and will let you know once it is available.
Thank you
Regards
SmartAPI Team
Hello @Mastermind @trader_noob,
Apologies for the inconvenience.
Our tech team is working on solving this issue, we'll update you once it is resolved.
Regards
SmartAPI Team
The issue has been fixed. You can use websockets now. Thanks for your patience.
Regards
SmartAPI Team
Hello @Mastermind,
The issue has been fixed. You can use it know. Thanks for your patience.
Regards
SmartAPI Team
@notsoloud It is available for NFO. Please pass the correct exchange, symbol_name and token and it will give you the details.
Thank you.
Regards
SmartAPI Team
Hello @Mastermind,
Apologies for the inconvenience, our tech team is working to fix it asap.
We'll let you know once it is fixed.
Thank you.
Regards
SmartAPI Team
Hello @Mastermind @trader_noob,
Apologies for the inconvenience.
Our tech team is working on solving this issue, we'll update you once it is resolved.
Regards
SmartAPI Team
Hi @PandaTrade, You'll need to subscribe to specific tokens in the Websocket Streaming to get all these data points.
Our Websocket provides this information, please search for the requisite token.
Thank you
Regards
SmartAPI Team
@PandaTrade We use a different naming convention. Please tell us the Strike Price and Expiry so that we can help you find it.
All the data is present in Scrip Master file
Regards
SmartAPI Team
@sunil_modi are you passing your mobile MPIN in the password field? Please pass that here. We are working to change this nomenclature here.
Also, the secret key for TOTP is not the secret key generated along with the API key in the app. The string which you need to pass in the TOTP is the one generated below the QR code in TOTP Generation.
Hi @RK123,
We will check this with our tech team and let you know.
Regards
SmartAPI Team
@PandaTrade, Yes it is available for Index Options too. you just need to pass the correct exchange segment and token of the contract in the request body.
Please note that we donot have data of Expired contracts as of now.
Regards
SmartAPI Team