Static IP for API allowlist: a fixed IPv4 your partners can trust

Why do APIs and firewalls ask for a static IP?

APIs and firewalls ask for a static IP because a known source address is a simple second check on top of a key or password. If a key leaks, a request from an unknown address is still refused.

Common places that use an IP allowlist:

• Partner and supplier APIs: logistics, inventory, wholesale catalogs and data feeds.
• B2B dashboards that accept logins only from a customer's registered addresses.
• Cloud firewalls and security groups that open SSH, a database port or an admin panel to listed IPs.
• Staging and preview servers that should not be public.
• SaaS admin consoles with an optional "trusted IPs" setting.

Home and office connections often change address, and cloud functions or CI runners use shared, changing ranges. A rented IP gives all of them one stable exit.

Which two allowlists are involved?

Two different allowlists meet in this setup, and mixing them up is the most common support question.

If your machines have changing addresses, skip the proxy allowlist and use the username and password instead. Username and password, or an IP allowlist (up to 10 IPs).

How do I route API calls through the static IP?

Route API calls through the static IP by setting it as the HTTP(S) or SOCKS5 proxy of the client that calls the API. Most HTTP libraries, curl and many tools read a proxy setting or the HTTPS_PROXY environment variable. First confirm the exit address with a public echo service, then call the partner API. The addresses below are documentation examples; your real IP, port and credentials are in your account.

# 1. The address the partner will see
curl -x http://USERNAME:[email protected]:8000 https://api.ipify.org

# 2. Same proxy for every tool in this shell
export HTTPS_PROXY=http://USERNAME:[email protected]:8000
curl -H "Authorization: Bearer $PARTNER_TOKEN" https://example.com/api/v1/orders

What happens to the allowlist when the rental ends?

The allowlist keeps working as long as you keep the same IP, so renew before the end date. Each rental lasts 30 days from delivery. Renew from your account before the end date; keeping the same IPs after a rental ends is not guaranteed.

A safe routine for allowlisted access:

1. Rent two IPs, not one. Give the partner both addresses. If one has to be replaced, the other keeps the integration running.
2. Note the end date shown next to each IP in your account, and renew a few days early.
3. Keep the partner's change process at hand. Know who updates their allowlist and how long it takes.
4. Test after each renewal with the echo call above.

If an IP does not work or is unusable for a lawful use, write to support: we fix it or replace it with an IP in the same country, subject to stock. A replacement IP is a new address, so it needs a new allowlist entry.

When is a rented proxy IP the wrong choice?

A rented proxy IP is the wrong choice when the service you want to reach is on our blocked list or needs a permanent address. Banking, government and payment-portal sites are blocked on every IP, so bank and payment API allowlists are not a use we support.

Also consider other options when:

• You run your own servers in the cloud: a static address from your cloud provider, attached to your own NAT gateway, keeps the traffic inside your infrastructure.
• You need IPv6: IPv4 only. IPv6 proxies are not sold yet.
• You need the same address for years: a 30-day rental can be renewed, but it is not an address assignment you own.