@sujith and @themohammedfaisal
Did you guys notice the briefcase mismatch in the kite app (UI)? Please let me know if not showing the holdings in the briefcase is an expected behavior
Thanks
@sujith and @themohammedfaisal
Please notice that this * symbol is causing a misrepresentation even in your app.
Though I have certain holdings of SUNPHARMA, the briefcase symbol is not shown (which indicates holdings), right? Are you planning to …
@sujith
Thanks for sharing the link. But, since I have traded using APIs for almost 3 months now, I guess I know how it works. My concern is more specific for today around 9.44 am - Our app credentials were to expire today. So, on the day of expiry…
@sujith and @themohammedfaisal
Regarding * accompanying the symbols for companies with corporate action, like SUNPHARMA* shown at the top of this discussion, why don't you indicate that differently? Maybe like you show EVENT (in case there is some…
@trade_then
Thanks for joining the discussion
Did you move to websocket coz Postbacks was more painful (glitchy) or did you start off with websocket itself? - We are planning to stick with Postbacks as we might have to cater to multiple accounts (t…
@sujith
Just to get a better picture, how did others deal with missing postbacks on 26th of June? Why haven't anyone posted a discussion regarding this, except for us? We find it kinda difficult to comprehend the situation...
@Vivek @rakeshr @sujith
Please note that I have never generalized (happening all the time) the exception. In fact, the topic name itself has "Intermittent" in it. My response was in clarification to Sujith's concern about why only we are facing iss…
@sujith and @Vivek
Sorry. I don't understand this ambiguity. There were a few postbacks that were lost on 26th June 2020. Right @Vivek ?
I thought Vivek is with Zerodha and he agreed to this. Am I wrong?
@Vivek and @sujith
I don't even know how to react to this. Postback failures cost us a lot of orders and money. At least an apology was in order I guess. This time at least we have a consensus that indeed some postbacks weren't sent at your (Zerodh…
@sujith
Some of the order IDs for which we didn't receive Postback (For your reference):
200626200399385
200626200399376
Some of the order IDs for which we have received Postback (For your reference):
200626200428393
200626200909108
Thanks
@themohammedfaisal and @sujith
Thanks for the clarification. Is it possible to revert back to the previous version and keep it simple? - It kinda becomes annoying to handle changing tradingSymbols and exchanges. Y don't we just let the traders deci…
We have never placed an order for FINOLEXIND. All our orders till date have been placed for FINPIPE in NSE. However, current Holdings show that all our shares are under FINOLEXIND. We even get Instrument invalid while placing an order for FINPIPE fo…
But @sujith our positions and holdings are only in NSE. Is there some cross-exchange information sharing or something?
And also what about FINPIPE and FINOLEXIND?
@rakeshr @sujith
We do get the tag in a postback and we are using it. Thanks a lot for the clarification though. However, what about this field "tags"? From the JSON you have posted, it seems to be a list of tags that the client has passed. However…
Thanks for the quick reply @sujith
So, what is the mechanism to handle multiple clients? How do businesses which have multiple hundreds/thousands of clients scale with this restriction?
@sujith
Do you have any logs with you that confirms that you have sent the json and received a 200 response from our endpoint? - If you share that, we can discuss further to see what's causing this erratic dropping.
@sujith
Attaching the SUCCESS response from the postback URL. You can use similar methods to verify. Even before this we have tested using Postman. Please let me know if you have any further questions.
@sujith
As I said, please don't make GET request. And, you get METHOD NOT ALLOWED (405) message only if you are able to directly hit the endpoint with your GET request, not if we have a proxy in-between. Please correct me if I am wrong. Please try…
@devarajh
Please don't share your postback IP publicly. Might not be safe. Somebody with malicious intent might hit your endpoint with false responses.
@sujith
I beg to differ on the method you have used to verify our endpoint. Unless you cURL a valid json POST request to our endpoint during market hours and not get a valid response, I don't think it is correct to conclude the service is not up an…
@sujith
Please note that after market hours, even the POST requests won't be answered with 200 but only 502. Only during market hours, POST requests are answered with 200 response after successfully logging the json as the very first step.
@sujith
Please don't do a GET request. We are not answering GET requests on that URL (endpoint). We are expecting and processing only POST requests on that endpoint.
@sujith
If it helps, I could share my entire day's logs with you. I am just trying to understand where the entire system might be failing. I log the entire json as soon as it hits our endpoint. Since the endpoint is hosted on AWS, I find it very di…
Fair enough @sujith
My bad. My apologies for my statements.
However, could you please tell me how you confirm that our service was unreachable? Our service runs on AWS and afaik, the service can't go unreachable. Especially when I receive the postb…
@sujith
Could you please reply?
One more instance of the same issue (12:04:10 on 2020-05-21). I am confident that this behavior is a consequence of a fault at your end. Please check. This is becoming a lot of late. Costing us quite some money here.…
@sujith Same issue today at 09:46:44 (2020-05-21)
OrderID - 200521200271731
Please confirm whether there is an issue at your end.
Note that I have received postback for both the prior and subsequent orders.
Dear @sujith
Even I didn't receive postback for a particular COMPLETE order at 14:01:15 today (2020-05-20)
OrderID - 200520201281119
Please check at your end
