Dhanhq version 2.0.2 vs 2.10

APIs, Automation, Algos & Code
1

@Dhan @Hardik , HI dhan please check the dhanhq lib after recent update of option historic data, market depth to 200, I am unable to get data properly for testing,

1.for example in option historic data, I got spot value same through out the day after 14 oct onwards even changed time 90 days to 15 days same result.

  1. Market depth no separate request code for 200 market depth is their in annexure and only url is different but i checked so many times 20 market depth only working but 200 market depth connecting but not returning any data.

  2. Today while I tried to test market feed script, at least in past they used to return closing data, but today no data returned. Once check these issues most of codes used to work in past today not got any data from dhanhq even after connecting and subscribing.(may be dhan team doing maintainance or upgrades please check once).

  3. Last but not least python package upgradation plan: dhanhq · PyPI, as more and more upgrades your team are adding once check versions and if possible upgrade, why because i am observing some times old versions are not able to keep up with upgrades and crashes, so kindly note this and check upgradation of python lib.

2

Hey @Rem_555 ,

  1. For the historic data part, we request you to please share the detailed query over help@dhan.co so we can understand it better and assist you accordingly.

  2. For the 200-level market depth, please use the below request structure (this will also be updated soon in the documentation):
    {
    “RequestCode”: 23,
    “ExchangeSegment”: “NSE_EQ”,
    “SecurityId”: “1333”
    }

  3. Please try again today if you still face any error, do share your request structure over email for us to check.

  4. Noted your feedback on the Python package upgrade we’ll pass it on to the concerned team.

3

same issue with 200 level data : I was trying to subscribe for 200 level data streaming through websocket but after connection was established , i couldn’t recieve the messages : i have used the offical documentation with requestcode 23 but still dosn’t work
I was trying to subscribe for 200 level data streaming through websocket but after connection was established , i couldn’t recieve the messages : i have used the offical documentation with requestcode 23 but still dosn’t work PS D:\test\backend> python debug_dhanhq_connection.py
:mag: Testing DhanHQ WebSocket connection…
INFO:auth:Environment variables loaded from .env file
INFO:auth:DhanHQ credentials loaded and validated successfully
:white_check_mark: Credentials loaded successfully
Client ID: 1103706176
Access Token: ********************…SYCMnrmGMQ
INFO:parser_config:Loaded parser configuration: {‘mode’: ‘corrected’, ‘enab
le_fallback’: True, ‘log_parser_selection’: True, ‘validation_enabled’: True, ‘performance_monitoring’: False} INFO:parser_config::wrench: DhanHQ Parser Configuration:
INFO:parser_config: Mode: corrected
INFO:parser_config: Fallback Enabled: True
INFO:parser_config: Validation Enabled: True
INFO:parser_config: Performance Monitoring: False
INFO:parser_config: Using default configuration (no environment variables
set) INFO:parser_factory::white_check_mark: Initialized corrected parser as primary
INFO:parser_factory::arrows_counterclockwise: Legacy parser available as fallback
INFO:parser_config::rocket: DhanHQ Market Depth Parser Startup:
INFO:parser_config: Selected Parser: corrected
INFO:parser_config: :white_check_mark: Using corrected 200-level parser (RequestCode 23,
12-byte header) INFO:parser_config: :bar_chart: Features: 200 bid/ask levels, comprehensive valida
tion, compliance monitoring INFO:parser_config: :arrows_counterclockwise: Fallback enabled: Will switch to legacy parser if
corrected parser fails INFO:parser_config: :mag: Validation enabled: Comprehensive message validati
on active :link: Connecting to DhanHQ…
INFO:websocket_client:Connecting to DhanHQ WebSocket API…
INFO:websocket_client::white_check_mark: Connected to DhanHQ WebSocket API successfully
INFO:websocket_client::mag: Started DhanHQ ping-pong compliance monitoring
INFO:websocket_client::clipboard: Official requirements: Server ping every 10s, client response within 40s :white_check_mark: Connected to DhanHQ successfully
:satellite: Subscribing to RELIANCE (1333) on NSE_EQ…
INFO:compliance_logger::satellite: Attempting subscription: 1333 on NSE_EQ (RequestC
ode: 23) (correlation_id: 8af7eeb5) INFO:compliance_logger::white_check_mark: Subscription OK: subscription_request: RequestCod
e 23 (success) (correlation_id: 8af7eeb5) INFO:websocket_client:Sent corrected subscription (RequestCode 23) for 1333
on NSE_EQ INFO:websocket_client::white_check_mark: Successfully subscribed to 1333 on NSE_EQ for 200-
level depth INFO:websocket_client::bar_chart: Note: Only one instrument can be subscribed per co
nnection (DhanHQ 200-level API restriction) INFO:compliance_logger::white_check_mark: Subscription OK: subscription_success: RequestCode 23 (success) (correlation_id: 8af7eeb5) :white_check_mark: Subscription successful
:hourglass_flowing_sand: Waiting for market data (30 seconds)…

:chart_with_upwards_trend: Connection Statistics:
Messages received: 0
Connection state: connected
Ping count: 0
Pong count: 0

:warning: No market data received
This could be because:

  • Markets are closed or low activity
  • Access token doesn’t have market data permissions
  • Instrument is not actively trading
    INFO:websocket_client:Disconnecting from DhanHQ WebSocket API…
    WARNING:websocket_client:WebSocket connection closed
    WARNING:websocket_client::arrows_counterclockwise: WebSocket disconnected - initiating reconnectio
    n… INFO:websocket_client::arrows_counterclockwise: Reconnection attempt 1/3 in 1 seconds…
    INFO:websocket_client::white_check_mark: Disconnected from DhanHQ WebSocket API
    :electric_plug: Disconnected from DhanHQ
4

Hey @Venkata_Krishnasai_A ,

We would like to inform you that, as of now, we do not provide Python code for this. However, you may use the base request structure given below
{
“RequestCode”: 23,
“ExchangeSegment”: “NSE_EQ”,
“SecurityId”: “1333”
}

5

image
image1260×537 42 KB

This is the screen shot of option data output irrespective of expiry code and date time period same output comes , i.e., after 14 oct spot price remains same throughout the day for 15 oct one spot price, next for 16 oct another spot price, in real time spot price changes minute to minute .But here in out put same thorough out the day.

Coming to 200 market depth the response header need to checked once, why because i have doubt as both 20, 200 has same request code may be we are getting both data which overlapping and causing such no response once confirm this also so that we can check 200 phrasing output.

6

Hey @Rem_555 ,

If you are fetching data using the endpoint https://api.dhan.co/v2/#/operations/optionchart, we have replicated the same and observed that the spot price changes at minute intervals. If you are still unable to receive data properly , please share the request structure with us over email at help@dhan.co.