@Hardik , Request code 16 is for wss end right as per documentation?
Pls check and advise. wss is not disconnecting even after sending rc16. subscribe/unsubscribe is fine
@Hardik , Request code 16 is for wss end right as per documentation?
Pls check and advise. wss is not disconnecting even after sending rc16. subscribe/unsubscribe is fine
Hi @Hardik , any link to working example of wss v2 is highly appreciated.
As per v2 docs, Rc (Request code) 15 is for subscribe, Rc 16 is for disconnect wss completely. but Feed Request code page says differently.
Also when i send Rc 15 for nifty, bank nifty, getting back packets, Rc 17 is also working. but Rc 21 is not sending back response.
clarity on this needed. Thanks
Hello @TraderX
Let me take a look into this discrepancy, might be in documentation.
Thanks @Hardik , if possible, pls check and let me know about Full Packet response in Websocket v2 as well.
For Request code 15, 17, getting packets as requested. but for 21, not getting the full packet which has market depth.
Hello @TraderX
The Full Packet response is working fine. Are the other modes working for you in V2?
Hi @Hardik , sending the following message in websocket v2.
Subscribe Codes 15, 17 working fine
Unsubscribe Codes 16, 18 working fine
However, Codes 21, 22 to get full packet is not working both in postman (binary response) and via code (decoded). not sure what’s going wrong. kept the payload same for all three packets. Tried during both live and off hours
{
“RequestCode”: 15,
“InstrumentCount”: 1,
“InstrumentList”: [
{
“ExchangeSegment”: “IDX_I”,
“SecurityId”: “13”
}
]
}
PFA
Also Disconnect Websocket is also not working
Hello @TraderX
I tried this for other instruments, not for IDX_I. Let me try to replicate this and get back to you.
On the disconnection code, try with 12. I will update documentation as well.
Code 12 worked for disconnect with 1006 Abnormal Closure: No close frame was received… Ideally it should have been 1000 Normal Closure, but this should be fine and does the job.
Now only the full packet subscribe for IDX_I is needed to be checked @Hardik
Also just wanted to send a big thanks for your team for v2 apis. Although there are hiccups which will improve over time, its far better than v1
@Dhan , @Dhan_Cares , @PravinJ
Hello @TraderX
Checking the full packet subscription for Index today. Thank you for kind words, glad to know you have already moved to v2.