A static IP for API whitelisting. Set it once, forget it.
The API only answers calls from addresses on its allowlist, and your code doesn't run from one fixed address. TrueIP gives your outgoing calls a dedicated IP in Mumbai that stays the same.
"IP not allowed" is rarely about your code.
It worked on Friday. On Monday every call gets a 401 or a 403 with something like "IP not allowed". You check the key, the headers, the clock. All fine. The request is simply coming from an address the API has never seen.
Where your code runs decides that address, and most places don't keep one. Home and office broadband in India is usually dynamic, and a lot of it shares public addresses through carrier-grade NAT. If your router's WAN address starts with 100. somewhere between 100.64 and 100.127, that's the shared range set aside for CGNAT, and you don't have a public IP of your own at all.
Cloud isn't automatically better. A new instance, a redeploy or autoscaling can bring a new outbound address unless you've paid for a fixed one. Serverless functions and many PaaS platforms send traffic out through shared pools that change without notice and that other customers use too.
Allowlists themselves differ as well. AWS security groups, Cloudflare, GitHub and Microsoft Entra accept IPv6 ranges. Stripe's API key IP restrictions take IPv4 addresses only. So the address you pick has to be both fixed and the right kind.
A fixed outbound IP in three steps.
- 01
Get a dedicated IP
Pick IPv4, or IPv6 if the API's allowlist accepts it. Pay online and the IP is assigned in minutes.
- 02
Add it to the allowlist
Paste the address into the API's IP allowlist, or send it to the provider if they manage the list for you.
- 03
Check the route
Set the proxy in your HTTP client, then run curl -x http://USER:PASS@HOST:PORT https://ifconfig.co. It should print your TrueIP address.
Proxy the calls that need it. Nothing else.
TrueIP is an authenticated HTTP proxy. Point the client for the IP-restricted API at it, or set HTTPS_PROXY for a whole process, and those calls leave from your fixed address.
- ✓ Any language or tool that supports an HTTP proxy
- ✓ HTTPS stays encrypted end to end through the proxy
- ✓ Separate IPs for staging and production if you want them
- ✓ Credentials for every IP downloadable as CSV
What a static IP for APIs gives you.
One address, only yours
A dedicated IP reserved for your account. Never shared with another customer and never rotated, so the allowlist trusts your calls and nobody else's.
Same IP on renewal
Renew on time and the address doesn't move, so allowlists you've set up keep working.
IPv4 or IPv6
IPv4 for allowlists that only take IPv4. IPv6 at a quarter of the price where IPv6 is accepted.
Per-IP credentials
Each IP has its own host, port, username and password, so projects and environments stay apart.
Encrypted end to end
HTTPS calls stay TLS encrypted through the proxy. We see a destination host, never your tokens or payloads.
Priced per IP. Match the allowlist.
If you don't know what the allowlist takes, start with IPv4. It's accepted everywhere an IP allowlist exists.
IPv4 dedicated
Works with every allowlistThe safe pick when the platform only takes IPv4, or you don't know yet. Same price per month on any term.
- Dedicated IPv4, never shared or rotated
- Per-IP host, port, user and password
- Same IP kept across renewals
- CSV export of credentials
- GST invoice on every payment
IPv6 dedicated
Locked for lifeFor allowlists that accept IPv6, like AWS security groups, Cloudflare or Microsoft Entra.
- Unique /128, never shared or rotated
- Per-IP host, port, user and password
- Same IP kept across renewals
- Price locked while you stay subscribed
Two quick questions tell you which one fits: use the plan finder.
API whitelisting questions.
Will the IP ever change?
No. The address stays the same for your whole term and on every renewal. Renew before it expires and your allowlists never need updating.
Do I get a GST invoice?
Yes, on every payment. IPv4 is ₹200 + 18% GST (₹236 a month) and IPv6 is ₹50 + GST (₹59). Add your GSTIN in the portal to get it in your company's name.
Is my data visible to you?
No. Your connection to the API is TLS encrypted end to end. We see encrypted traffic and the destination host, not your tokens, headers or payloads. Breaking TLS would trigger a certificate error, so it can't happen silently.
IPv4 or IPv6 for this?
Whatever the allowlist accepts. AWS, Cloudflare, GitHub and Microsoft Entra take IPv6. Stripe's key restrictions take IPv4 only, and many Indian banks and government APIs don't mention IPv6 at all. When in doubt, IPv4.
Does it work from serverless functions?
Yes, as long as the function can make an outbound HTTPS call through a proxy. Set the proxy on the HTTP client in your function code.
Can the API call me back on this IP?
No. TrueIP only carries your outgoing calls. It doesn't accept incoming connections, so webhooks still go to your own server's URL.
Guides for this setup
Why your API says "IP not whitelisted" and how to fix it for good
Your API key is fine but every call fails with "IP not whitelisted". Here's how to find the address the API sees, why it changed, and how to stop it changing.What is CGNAT, and why your home internet has no real IP address
If your router's WAN IP is in the 100.64 to 100.127 range, you're behind CGNAT. What that means, how to check it, and how to get a real, fixed IP address.IPv4 vs IPv6 for whitelisting: which one will your platform accept?
Some allowlists take IPv6, many still want IPv4. Which platforms accept which, how to test yours in two minutes, and when ₹50 IPv6 beats ₹200 IPv4.More setups on the use cases page, or find the right IP type in 30 seconds.
One IP for every allowlist. Live in minutes.
A dedicated IP from Mumbai: IPv4 for ₹200 + GST a month, or IPv6 for ₹50 + GST. Same address on every renewal.