Posts made by Moderator_2

Hi @Asp9999

Apologies for the delayed response.
Kindly reverify on the private key intiated on the API header and let us know if the issue still occurs.

Regards,
SmartAPI team

hi @nitish-bane

Apologies for the delayed response.
We are trying to reproduce the issue from our end, but we are getting the Websocket response in ms. Will update you asap for the same. Meanwhile kindly reverify on the business logic if any applied at your end is causing th delay.

Regards,
SmartAPI Team

Hi @vegybin

Apologies for the delayed response.
We are verifying on the issue, will update you as soon as possible.

Regards,
SmartAPI team

Hi @Asp9999

Kindly reverify if the totp has been enabled, and mpin and totp has been passed properly and update if the issue still occurs
Please let us know if you are trying to login for first time.

Regards,
SmartAPI team

Hi @dhanesh007

Thank you for notifying us on this issue. We provide OHLC value on Historical API, Websocket streaming, Live Market Data API(Full Mode) and so. Kindly let us know if the issue occurs on which this discrepancy has occurred.

Regards,
SmartAPI team

hi @dipeshbodas

Kindly reverifying the issue with below function and let us know if connection timeout still occurs.

public void smartStreamTicker(String clientId, String feedtoken, SmartStreamListener smartStreamListener,Integer delay,Integer period) throws WebSocketException {
SmartStreamTicker smartStreamTicker = new SmartStreamTicker(clientId,feedtoken,smartStreamListener,delay,period);
smartStreamTicker.connect();
}
smartStreamTicker(clientId, feedToken, smartStreamListener,10,10);

Regards,
SmartAPI team

Hi @dipeshbodas

We are reverifying on the issue. Will update you for the same.

Regards,
SmartAPI team

Hi @sujaygaitonde

As we verified on python SDK 1.4.8 version, we are unable to reproduce the issue from our end. Please verify if any changes has been made at your end.

Regards,
SmartAPI team

Hi @thunder123

Please let us know which SDK version is consumed at your end.
Kindly make sure if the issue occurs on recent SDK version 2.2.3 and let us know if the issue still persists

Regards,
SmartAPI team

Hi @anudeep-atyam

Historical API is working from our end. Please verify if the request has initiated within rate limiting.
Kindly share us error if the issue still occurs.

Regards,
SmartAPI team

Hi @ashigro

Apologies for the delayed response. We are verifying on this matter. Please confirm if the issue consistent or intermittent from your end.

Regards,
SmartAPI team

Hi @vinodsrao

Apologies for the delayed response.
Angel One ID is required to consume our provided smartAPI.

Regards,
SmartAPI team

Hi @A51440435

Apologies for your trouble. Is there any specific API, "Invalid Token" issue has been faced. Please let us know

Regards,
SmartAPI team

Hi @dipeshbodas

We have fixed the timeout issue on our SDK. Kindly update from the recent version and let us know if the issue still occurs

Regards,
SmartAPI team

Hi @jaideep-siddula

Please note if it helps
When initially SL order is placed, the order type will be Stop Loss, After the order got placed and in open, type will be changed from Stop Loss to Limit.
So the order that is in open, will be under variety of normal order and order type will be limit.

Regards,
SmartAPI team

Hi @A51440435

Apologies for the delayed response. Kindly share us the client code/API request and issue timing to analyze on this matter

Regards,
SmartAPI team

Hi @greatworld

Action param on Websocket request represents zero to unsubscribe(feed stops) and one to subscribe(feed starts) the scripts.
For some scripts, we may not notice any changes on the ticks since there wont be any trade occurring for it. We provide feeds continuously that is received from exchange end.
If it is required to fetch data with latency time delay can be added. Kindly refer below
Ref:
https://masteringjs.io/tutorials/node/sleep

Regards,
SmartAPI team

Hi @sujaygaitonde

We have fixed the 'NoneType' object is not subscriptable error on recent SDK. Please update the recent python version smartapi-python 1.4.7 and let us know if the issue still occurs.

Regards,
SmartAPI team

Hi @matmart5

Trade Executed for current date alone can be fetched from trade history.

Regards,
SmartAPI team

Hi @ngk

On Websocket, as you are aware we allow three concurrent connection per client for anytime. And each of the three connection can subscribe for 1000 tokens. If these limit exceeds, the extra connection will be closed. While creating the connection, the limit needs to be set and the same needs to be closed properly after consumption.
Connection can be closed for many reason, as such network disruption, OS issue, library issue etc.
Please reverify on these and let us know if further help required.

Regards,
SmartAPI team