Navigation

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

    Static IP based API keys now live - Old flow still supported temporarily

    General Discussion
    6
    11
    57
    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.
    • N
      Ninad @admin last edited by

      @admin Thanks. Helps a lot. Since we have time, migration to a new API key will be easier now.

      1 Reply Last reply Reply Quote 0
      • S
        stanly_thomas last edited by

        Can family members use same static IP? I have seen other brokers mentioning about it.

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

          @admin Where to get the oauth documentation?

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

            @openalgo OAuth will be live soon. Will keep everyone updated of the same.

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

              @stanly_thomas As of now, static IP cannot be shared within the family members. We will get the feature live soon.

              1 Reply Last reply Reply Quote 1
              • S
                Sachin0521 last edited by

                Hello SmartAPI Team,

                Thank you for the update on the new static IP implementation. I have a question regarding how this applies to my specific use case.

                I operate an algorithmic trading platform that serves 50 different clients. All orders for these individual client accounts are executed from our central server, which has a single static IP address.

                My question is: After I whitelist our server's single static IP, will I be able to successfully place orders for all 50 of my clients using their respective API keys? I am concerned because the orders for many different accounts will originate from the same IP address.

                Could you please clarify if your system supports this "one-to-many" model (one whitelisted IP placing orders for multiple client accounts)?

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

                  @sachin0521 Since you are an algo provider, as per guidelines of SEBI, you need to empanel with exchanges. Once you are empanelled, you can get into a commercial agreement with brokers.

                  The static IP flow here is for the tech savvy clients who are making their own algos by coding and using smartAPI to trade.

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

                    @admin The procedure to register the static IP address has changed from what you had posted on this forum earlier. Before you implemented "new login", I had already created an API key with my static IP address on the old login link. Now I'm not able to use that IP address since it's already in use. Even when I disable the old API key, I'm not able to use the IP address. Why have you created so much confusion? Can I continue using the old API key since it's already linked to the static IP? Please clarify.

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

                      @pari You can use the same API key that you had created earlier.

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

                        @admin Ok. Thanks for the clarification. Also please update your documentation for rate limits. The documentation still says 20 orders per second.

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