Starting August 1st, NSE's new rule allows only one static IP per API. If you're managing two or more accounts, you might assume you need to run multiple virtual machines with one static IP in each. However, you can actually attach multiple static IPs to a single VM. I successfully implemented this in Google Cloud Platform (GCP) by adding multiple network interfaces.
Sharing this tip for anyone who might find it helpful!
but this will then be like number of static IPs required == number of accounts handled? What will happen to platforms who have thousands of users onboarded
Ok thank you. I am using linode and I can see a option to get multiple static IPs. That requires additional cost though. But I am unclear on the fact that, if I get 5 static IPs for my VM, how come I can map them to my api keys for 5 different accounts. I am not sure about this.
its not necessary unique ip should assign on same system where algo is running, ip can be assigned on any big hardware machine / datacenter and traffic will route through them.
means algo provider will only need to worry for service subscription, and hardware and ip will be manage by 3rd party service provider like us.
I have several IP addresses on my virtual machine. But I need to use python to bind my API based orders to a specific source IP address on your machine before sending the request. Any suggestions on how to do that. Code would be very helpful.
Code to bind a kite instance to a specific IP address, specifically
What will happen to platforms who have thousands of users onboarded
I am using linode and I can see a option to get multiple static IPs.
That requires additional cost though.
But I am unclear on the fact that, if I get 5 static IPs for my VM, how come I can map them to my api keys for 5 different accounts.
I am not sure about this.
Instead they can easily purchase static ip from vendors and use unique ip for each client.
That unique ip should be ip of the machine for that user where api will be executed
means algo provider will only need to worry for service subscription, and hardware and ip will be manage by 3rd party service provider like us.
May not be interested route my algo/api traffic through third party
but just of info: https request is fully secured and noone can see the traffic content.
Code to bind a kite instance to a specific IP address, specifically