Now Live: API Regulatory Changes on DhanHQ

Product Announcements 🔈
21

your problem solved or not

22

There are still pending issues:

  • I’m not able to modify my primary IP. It keeps showing that it can only be changed after six days, which I’m not sure why, because it was changed last time eight days ago. This is still unresolved.

  • My secondary IP was my static IP which I purchased from my ISP provider. When I was placing an order using that IP, it was not taking the order and showing “invalid IP” because it was only considering my primary IP, which is IPv6, which I don’t have anymore. I think this is because websites are always giving priority to IPv6.
    Then I changed my OS configuration to always give priority to IPv4, and after that, while placing the order it started considering my secondary IP, since I already had IPv4 set as a secondary IP. So somehow I was able to resolve this. But still the first issue remained as it was.

  • I’m not able to modify my buy limit or take profit drag-and-drop lines using the UI for an order placed using API. If I want to modify those take profit or stop loss lines, I have to manually cancel the previously set take profit valuesfrom the UI, and then put TP and SL manually.

  • I’m not able to place stop loss type orders using the API. It just keeps showing a validation error. {‘status’: ‘failure’, ‘remarks’: {‘error_code’: ‘DH-906’, ‘error_type’: ‘Order_Error’, ‘error_message’: ‘Basic Validation Failed’}, ‘data’: ‘’}. It was working fine before 1st April.

CC @Hardik

23

Hello @vinay_rana8727

  1. Let me take a look into this. Can you share your Client ID on DM, will directly look into this
  2. This should not happen, given we accept both IPv4 and IPv6, without any preference.
  3. This is a limitation from the exchange itself (particularly with NSE) - API based orders are currently not being allowed to modify. We have already informed this to exchange and waiting for their approach on this.
  4. Are you using Stop Loss Market order by any chance here?
24

@Hardik @Poornima - Is Full Market Depth down?

  • “Is 200-level depth (wss://full-depth-api.dhan.co/twohundreddepth) enabled?”

  • “I’m getting ResetWithoutClosingHandshake on every connection attempt. My 20-level depth works fine.

  • Tried even with this Dhan Python SDK URL but still failing by following the below request.

URL: wss://full-depth-api.dhan.co/?token=&clientId=&authType=2
Subscribe JSON: {“RequestCode”:23,“ExchangeSegment”:“NSE_FNO”,“SecurityId”:“40977”}
Error: Protocol(ResetWithoutClosingHandshake) after ~5-30 seconds
Behavior: Connection establishes, subscription sent, server resets without data
Note: 20-level depth works fine. Only 200-level fails consistently.

{“timestamp”:“2026-04-07T12:48:38.008660+05:30”,“level”:“WARN”,“fields”:{“message”:“depth-200lvl-FINNIFTY-ATM: connection failed — will reconnect”,“attempt”:31,“err”:“ConnectionFailed { url: “wss://full-depth-api.dhan.co/twohundreddepth”, source: Protocol(ResetWithoutClosingHandshake) }”},“target”:“dhan_live_trader_core::websocket::depth_connection”,“threadId”:“ThreadId(7)”}
{“timestamp”:“2026-04-07T12:48:38.008680+05:30”,“level”:“WARN”,“fields”:{“message”:“depth-200lvl-MIDCPNIFTY-ATM: connection failed — will reconnect”,“attempt”:31,“err”:“ConnectionFailed { url: “wss://full-depth-api.dhan.co/twohundreddepth”, source: Protocol(ResetWithoutClosingHandshake) }”},“target”:“dhan_live_trader_core::websocket::depth_connection”,“threadId”:“ThreadId(12)”}
{“timestamp”:“2026-04-07T12:48:38.013728+05:30”,“level”:“WARN”,“fields”:{“message”:“depth-200lvl-BANKNIFTY-ATM: connection failed — will reconnect”,“attempt”:31,“err”:“ConnectionFailed { url: “wss://full-depth-api.dhan.co/twohundreddepth”, source: Protocol(ResetWithoutClosingHandshake) }”},“target”:“dhan_live_trader_core::websocket::depth_connection”,“threadId”:“ThreadId(12)”}

25

@Hardik I have sent you my client id.

  1. Are you using Stop Loss Market order by any chance here? - Yes. I am using order_type=DHAN_OBJ.SLM.… It was working fine before 1st April. Was there any changes made after 1st April?

  2. API based orders are currently not being allowed to modify - Please let us know based on Exchange response.

  3. This should not happen, given we accept both IPv4 and IPv6, without any preference - I think this is host specific. On my Windows machine, IPv6 was being prioritized because my ISP provides IPv6 and IPv4 both. As a result, all order requests were being sent over IPv6, which is dynamic and not static.

    To resolve this, I changed the priority to prefer IPv4 over IPv6 using the following command:

    netsh interface ipv6 set prefixpolicy ::ffff:0:0/96 60 4

26

@Hardik Any update from the exchange on the issue where orders placed via the Dhan API cannot be modified through the DHAN UI?