Navigation

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

    nifty banknifty token not found?

    General Discussion
    0
    17
    111
    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.
    • A
      A458898 @Mnagesh last edited by

      @Mnagesh are these working?

      R 1 Reply Last reply Reply Quote 0
      • R
        ramk @A458898 last edited by

        @A458898
        this is not working. Clearly a let down by Angel API team

        1 Reply Last reply Reply Quote 0
        • Mnagesh
          Mnagesh @vijaykumarsaurav last edited by

          @vijaykumarsaurav said in nifty banknifty token not found?:

          AB1018

          same error here too

          for index better to use NSEpy

          In angel one we get details for only tradable instruments

          Now I am full time Algo Trader and successfully developed my own Apps for my personal use.

          R 1 Reply Last reply Reply Quote 0
          • R
            ramk @Mnagesh last edited by

            @Mnagesh
            why should we use nsepy for a feature which was working until this friday. Angel has to restore this feature at the earliest. My entire order placing code is in a mess because of this breaking change

            Mnagesh R 2 Replies Last reply Reply Quote 0
            • Mnagesh
              Mnagesh @ramk last edited by

              @ramk i am just telling the alternate solution.

              I am not responding on behalf of Angel one

              I am just a client using smartapi for my personal apps .

              I trade nifty and banknifty futures .

              So for me nifty future itself is the reference for index too indirectly.

              I agree angel will not concerned about our issues very seriously.

              So what can we do. Somehow we need to resolve the issue by our own methods or
              alternate solution should be found for the issues.

              So I mentioned to use nifty future asas reference indirectly or use NSEpy.

              It is left to you to consider the same or keep depending on angel one until you get the solution.

              Good luck

              Now I am full time Algo Trader and successfully developed my own Apps for my personal use.

              R 1 Reply Last reply Reply Quote 0
              • R
                ravitandur @ramk last edited by

                @ramk yes, you are correct. Just like you there are many users who heavily depends on the master JSON for getting the required symbol tokens. Just for the silly mistakes done by Angel team we can't change our implementation which is working from ages.
                If these kind of issues continues, at least users like me will be moving out from Angel platform one day.
                Funny and frustration is, no one from Angel is not responding on this priority issue which is impacting many users.

                1 Reply Last reply Reply Quote 0
                • R
                  ramk @Mnagesh last edited by

                  @Mnagesh
                  Understood your alternate solution. Nothing against you. My post was about Angel API team's mismanagement.

                  1 Reply Last reply Reply Quote 0
                  • R
                    ramk last edited by

                    have sent a mail to api@angelbroking.com. Lets see if that helps

                    1 Reply Last reply Reply Quote 0
                    • R
                      ramk last edited by

                      attention : @Taapas @bhaveshjain

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

                        Hi everyone,

                        Our data vendor has stopped publishing Nifty and Bank Nifty indices data. We have shared the logs with them and are working on having this fixed. We regret the inconvenience.

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