validity_ttl added to orders JSON

You've added a new field "validity_ttl" to the orders data JSON recently, due to which our order processing system has been erroring out. It would be great if you can announce such additions/changes in the developers' forum (or even better, send an email to developers) before making the update.

Ramakrishnan S
  • sujith
    sujith edited December 2021
    Adding a new field shouldn't break the existing system. All our apps use the same APIs and it hasn't broken after adding a new field. Maybe you need to change the way you parse orderbook.
    This feature is currently in private beta, so you are seeing this. We will announce it when publicly released.
  • MangeshD
    @sujith sir same is the problem with our app it constantly started throwing error unknown column "validity_ttl", It would be great if announce for beta updates too.

    Thanks & Regards
    Mangesh D. Dave
  • ramatius
    @sujith The order JSON is parsed into a db query as the first step. The fields are expected to be as given in the API documentation. Checking each field for validity is expensive and slows down the system. Pls use your internal testbed for private beta updates. If you are introducing the change in the production API server, pls inform the developers before you make the change. Thanks.
  • sujith
    The recommended way to use APIs is to parse the fields that are documented.
    If it is a field name change then we will definitely announce it. But adding a new field shouldn't break the existing system.
    The recommended way of using Kite Connect is to write programs in such a way that it shouldn't break when a new field is added. That’s how all our systems work.
Sign In or Register to comment.