Posts made by admin

@nimish05z Please share your api request snippet.

@anand-n04 The status line is: HTTP/1.1 429 Too Many Requests.

One client is only allowed to create 3 connections only.

@darshil611 You can clear you cache and try again.

@pari You can use the same API key that you had created earlier.

@swogatpradhan22 It does provide OI data. For scrips where OI is not applicable, eg. cash, the OI will be shown as 0.

@popular003 As of now, you will have to trade via web or app in such stocks. We will be coming up with a solution soon.

@dibyendu1997 we do not support cover orders via smartapi

@mahidaparth7 please use 'producttype': 'INTRADAY' instead of 'MIS'

@pareshbhatiya Place order is working fine. Please cross check the API key in your header for place order.

@mryash AG8001 comes due to invalid token. You need to log in daily and create a new JWT token daily to be able to use other APIs.

@smartapi-0 Web socket responds in hex. Please check using postman, and then use the websocket in your code.

@rahim1021 As per the exchange guidelines, it is mandatory to show a pop up message of all the cautionary messages and to capture user's consent on the order flow after the user reads all the messages.

This cannot be done on an API level. So, we do not allow such scrips from API as of now.

You can place orders in such scrips via app and web of Angel One.

@ananthapad all the orders placed after market go as AMO orders. You can read it here in the place orders section - https://smartapi.angelone.in/docs/Orders

@satishdwivedi Your screenshot is not visible.

@v52717774 This error comes when the API key you are mentioning in the header of the API request is not the same as the one you have generated or using which you have logged in and created a JWT token.

@sachin0521 Since you are an algo provider, as per guidelines of SEBI, you need to empanel with exchanges. Once you are empanelled, you can get into a commercial agreement with brokers.

The static IP flow here is for the tech savvy clients who are making their own algos by coding and using smartAPI to trade.

@dibyendu1997 please put API Key (not secret key) in the X-PrivateKey parameter. It should run.

@satishdwivedi This error happens due to following reasons:

1. API key used in login is not the same as API key generated
2. API key used in login is different from the API key used in other API's request.

Request you to check the same. In case you are still unable to figure it out, you can share the API request snippet and API key screenshot here.

Hi All, it has been fixed.

Hi all, checking the issue.