Option Greeks for SENSEX was not available

Request:

{
"name": "SENSEX",
"expirydate": "08NOV2024"
}

Response:

{
"status": false,
"message": "No Data Available",
"errorcode": "AB9019",
"data": null
}

@Ananth said in Issue with tick data when large number of tokens are subscribed:

@Moderator_1

@Ananth said in Issue with tick data when large number of tokens are subscribed:

I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

Though I tried both and none of them was matching with angelone candles

Note:

I've already tried Historical API (getCandleData) which is even worse.

It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

I absorbed that even angelone takes some time to settle down the candle data.

F.e
If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

@admin @admin123 @Moderator_1 @Moderator_2 @Moderator_3

@Moderator_1

I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

Though I tried both and none of them was matching with angelone candles

Note:

I've already tried Historical API (getCandleData) which is even worse.

It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

I absorbed that even angelone takes some time to settle down the candle data.

F.e
If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

@admin Not getting data from websocket for nse_fo since past few days

Only getting

{ak: 'nk', task: 'cn', msg: 'cn'}
{ak: 'nk', task: 'mw', msg: 'mw'}
{ak: 'nk', task: 'hb', msg: 'hb'}

@admin
Since 20 Feb 2023 getLtpData returns 500 response, Previously this used to works fine.

Request:

{"exchange":"NSE","tradingsymbol":"NIFTY","symboltoken":"26000"}

Response:

{"status":500,"message":""}

@admin
Getting below error while login

{
data: null
errorcode: 'AB1007'
message: 'Login Id or password is invalid'
status: false
}

My client id = A657868

I'm confused with below properties

variety = STOPLOSS
ordertype = STOPLOSS_LIMIT / STOPLOSS_MARKET

In my scenario I need to place a stoploss order against my open position, which should execute in market price once it touches triggerprice

@admin Can you give me a sample params for above scenario

@admin Could you please reply, Waiting for your response!

@admin Client Id: A657868