I’m facing an issue with order placement through my API integration.
Yesterday, orders were executing successfully with the exact same pay
load and parameters. However, today, the same payloads are failing with the following error:
ErrorType: Input_Exception
ErrorCode: DH-905
ErrorMessage: Missing required fields, bad values for parameters etc.
please someone helo me with this . i have lost 2trading days because of this already! @Shubham_Singh
Hey @Shashank_Sharma ,
As checked from our side, everything seems to be working fine. It looks like you’ve automated some of the fields, we request you to try once by hardcoding them.
You can also test using the below request structure to confirm if it works correctly:
{
“dhanClientId”: “xxxxx”,
“transactionType”: “BUY”,
“exchangeSegment”: “NSE_EQ”,
“productType”: “CNC”,
“orderType”: “LIMIT”,
“securityId”: “14366”,
“quantity”: 1,
“price”: 8,
“targetPrice”: 10,
“stopLossPrice”: 5,
“trailingJump”: 0
}
You may test the same here: Dhan API
Hey Shrutika,
Thank you for your response. i tried hardcoding as well..but still getting the same error. this payload has been working for me since 8months now and sudenly it stopped working. could you please help me a little deeper with solving this issue for me?
I am facing the same issue, the payload that was working till yesterday, suddenly is providing a Bad payload missing parameters issue
@Harshit_Prakash mine just got fixed apparently the stopped asking for correlationId in the payload. but they clearly mention that it is required in their API DOC. once i removed that from payload it started excutions
Hello, thanks for the update, i will try it without correlation id, but it was a key node for referencing automated trades, any idea what to use if not for correlation id @Shrutika_Poojari
Hey @Shashank_Sharma ,
We want to inform you that the correlation ID is not a required field it is only used to track your order.
You may check the same Super Order - DhanHQ Ver 2.0 / API Document
Hey @Harshit_Prakash ,
The correlation ID is just a reference key node, and currently, there’s no alternative to it for tracking automated trades .
Yeah, and now if using the correlation id is providing an error what can we do, its not even an optional attribute now.
Hey @Harshit_Prakash ,
We want to inform you that it is optional attribute. However if you are facing an error with the same, then help us with the request structure over mail help@dhan.co so we could run the same our and check on our end.
i dropped an email on friday with all the necessary information. called support as well and they said they would schedule a call but they have not. @Shrutika_Poojari
Hey @Shashank_Sharma ,
As discussed over call, we will replicate the provided request structure during market hours and update you accordingly.
can you tell me which structure you are going to test? so there is no confusion? @Shrutika_Poojari
Hey @Shashank_Sharma ,
We will execute the request structure you provided by hardcoding it.
No update yet, couldn’t execute the request structure? Not to mention i started having this issue since last friday, which i solved at my own end by removing correlation id. and now i have been able to trade without the correlation ID which is huge risk i am taking on my end, because DHAN didn’t leave me any choice. @Shrutika_Poojari
““We want to inform you that it is optional attribute. However if you are facing an error with the same, then help us with the request structure over mail so we could run the same our and check on our end.””"
" So you keep telling me and not able to proove. and now 3 days have passed. God nows you will change your request structure again to start mandating correlation id without any notification, and again put us API subscribed users in trouble. @Shrutika_Poojari
Hey @Shashank_Sharma ,
The correlation ID for super order should be <= 30 characters
hey @Shrutika_Poojari any response from you???
Your response is utterly unacceptable and reflects a shocking lack of professionalism toward your paying API users. You implemented a breaking payload change — enforcing a correlationId length restriction — without any prior notification, without changelog updates, and without documentation revision, directly impacting live production systems that rely on your platform.
I am not a casual hobbyist user — I am a paid subscriber who uses your API as a primary source of income. Because of your undisclosed change, my production trading system stopped executing orders, resulting in four days of operational downtime, mental exhaustion, and severe financial and emotional stress.
The fact that you now casually describe this as “a validation that was already implemented for other order types” is irrelevant and dismissive. The burden of backward compatibility and developer notification lies entirely with you. Making silent breaking changes to a live API violates every standard of responsible API management and developer ethics.
You failed to:
If this is how you treat your paid developers, it raises serious concerns about your internal QA, release management, and communication standards.
I demand:
If I do not receive a satisfactory response within 72 hours, I will be escalating this matter — publicly and through regulatory and consumer protection channels — with complete technical evidence of the issue, your delayed responses, and the direct impact on my operations.
This is not just about one field. It is about trust, reliability, and accountability, all of which you have failed to uphold. @Shrutika_Poojari
