If I hit the configured Postback URL directly in browser, I see request in our access logs but when I have order in COMPLETE, CANCEL, REJECTED, UPDATE state I do not see any Postback request coming to our access logs. Earlier it was working but in last few days I have seen it not working for us. Is there any scenario where Zerodha blocks Postback URL for a specific Api Key. If yes, please let me know if you can unblock the same at your end. Please help us resolving the issue.
When I login I can see Redirect URL reaching to our Web Server, I can see the request in Web Server logs. But when I place an open order and later cancel it. I do not see CANCEL Postback request in Web Server Logs. Please refer #251029200704170 order id, also refer attached order history screenshot.
Please verify whether you are placing the orders using the app’s API key. You will receive notifications only if the orders are placed through that key. You can refer to the API documentation.
I want to understand one more scenario, when I place an open order on IDEA-EQ at 9.00 price using my API. Later I modify price from Kite to 9.05, I do not get UPDATE Postback. I again modify price from Kite to 9.10, I get UPDATE Postback for 9.05. If I take it further and modify price from Kite to 9.15, I get UPDATE Postback for 9.10. Can you help me why I always get an older UPDATE Postback.
@ttsdev We have raised this issue with the concerned team. In the meantime, the suggested workaround is to use the postback message as a trigger to fetch the order book and verify the latest details, or alternatively, fetch the order history and check the most recent entry.
