Navigation

    SmartAPI Forum
    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Groups
    • FAQs
    • API Docs

    Order Placement and Data Fetching Issues since yesterday

    General Discussion
    0
    5
    49
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mudit236 last edited by

      @admin Many users have been facing errors while trying to fetch data and place orders via api since yesterday. A post was made yesterday as well without any response. The issue seemed to have resolved by afternoon but is there again today morning. Could we get some clarification as to why this is happening or when it will stop by?

      1 Reply Last reply Reply Quote 0
      • P
        pari last edited by

        @admin Waiting for an acknowledgement at least. Ignoring this issue is highly unprofessional.

        A 1 Reply Last reply Reply Quote 0
        • A
          admin @pari last edited by

          Hi @pari
          We are aware of the error being faced by clients. Our team is currently looking into the internal error issue and working towards a resolution. We apologize for the inconvenience and appreciate your patience as we work towards a solution.

          A 1 Reply Last reply Reply Quote 0
          • Y
            yash12392 last edited by

            @admin can you confirm what was the issue, I go very weird quantities back when fetching order book. Please confirm so our debugging becomes easier

            {'variety': 'NORMAL', 'tradingsymbol': 'BANKNIFTY02FEB2342800CE', 'symboltoken': '49406', 'transactiontype': 'SELL', 'exchange': 'NFO', 'ordertype': 'MARKET', 'producttype': 'CARRYFORWARD', 'duration': 'DAY', 'price': '0.0', 'squareoff': '0.0', 'stoploss': '0.0', 'quantity': '44444444444444444444444444444444444444444444444444', 'trailingstoploss': '0.0', 'disclosedquantity': '0', 'triggerprice': '0.0'}},
            
            1 Reply Last reply Reply Quote 0
            • A
              admin @admin last edited by

              @admin The issue is now resolved

              1 Reply Last reply Reply Quote 0
              • First post
                Last post