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

> Static IP for API allowlist: a dedicated IPv4 for partner APIs and firewalls, from $1.29 per IP for 30 days. No KYC, pay in crypto.

- URL: https://rackproxies.com/use-cases/allowlisted-api-access/
- Last updated: 2026-10-19
- Publisher: RackProxies (https://rackproxies.com)

Many APIs, B2B dashboards and firewalls accept traffic only from listed IP addresses. A dedicated datacenter IP gives your scripts, laptops and CI jobs one known address to put on that list.

**Quick answer — How do I get a static IP for an API allowlist?**

Rent a dedicated datacenter IPv4 and send your API traffic through it. **RackProxies** rents a static IP for API allowlist entries from $1.29 per IP for 30 days: one customer per IP, HTTP(S) or SOCKS5, in 22 countries. Your partner adds that address once; every machine you route through it shares it. No KYC, pay in crypto.

## What do you get for an allowlist setup?

| Attribute | Value |
| --- | --- |
| Allocation | Dedicated: during your rental, each IP is assigned to your account only and is not shared with other RackProxies customers |
| Rental | 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 |
| IP version | IPv4 only. IPv6 proxies are not sold yet |
| Protocols | HTTP, HTTPS (CONNECT) and SOCKS5 |
| Who may use the proxy | Username and password, or an IP allowlist (up to 10 IPs) |
| Delivery | Each IP is delivered as a line `IP:PORT:USERNAME:PASSWORD` in your account, exportable as TXT or CSV |
| Not supported | Allowlists of banks, government services and payment portals: Banking, government and payment-portal sites, plus SMTP (email-sending) ports 25, 465 and 587 |
| Price | $1.29 for 1 IP, $6.45 for 5 IPs, each for 30 days |

## 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.

| Allowlist | Who keeps it | What goes on it |
| --- | --- | --- |
| Your partner's allowlist | The API, dashboard or firewall you want to reach | Your rented RackProxies IP, often written as a /32 |
| Your proxy allowlist | You, in your RackProxies account | Up to 10 of your own IPs allowed to use the proxy without a password |

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.

*Check the exit IP, then call the API through it*

```bash
# 1. The address the partner will see
curl -x http://USERNAME:PASSWORD@203.0.113.24:8000 https://api.ipify.org

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

The [connection format page](https://rackproxies.com/docs/connection-format/) explains each field of the `IP:PORT:USERNAME:PASSWORD` line, and the [quickstart](https://rackproxies.com/docs/quickstart/) has Python and Node.js versions.

## 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.

## How many IPs should an allowlist setup use?

| Plan | Quantity | Price | Price per unit |
| --- | --- | --- | --- |
| 10 datacenter IPs | 10 IPs | $12.69 | $1.27/IP · 30 days |
| 50 datacenter IPs | 50 IPs | $33.75 | $0.68/IP · 30 days |
| 100 datacenter IPs | 100 IPs | $59.25 | $0.59/IP · 30 days |

In every plan: Dedicated IPv4: one customer per IP · 30-day rental, renewable · HTTP(S) and SOCKS5 · Username/password or IP allowlist · Billed per IP, not per GB

**Before you pay**

- You top up the price of your plan. The checkout asks for the plan price (less your balance), at least $25; anything left stays on your balance.
- Unused balance stays on your account and never expires. When a purchase costs less than the minimum top-up, the part added only to reach the minimum is refundable on request to support within 30 days of the payment, in USDT or USDC, as long as it has not been spent. The rest of the balance is not paid back, except where the law requires it.
- Credited once your payment is checked on the blockchain. Typical network confirmation time: BTC ≈ 20 min · USDT TRC-20 ≈ 1 min · USDT ERC-20 ≈ 5 min · USDC ERC-20 ≈ 5 min · ETH ≈ 5 min · SOL ≈ 1 min · LTC ≈ 15 min

## Questions about a static IP for API allowlists

### Is the static IP shared with other customers?

No. Dedicated: during your rental, each IP is assigned to your account only and is not shared with other RackProxies customers. That matters for allowlists: an address shared by many users would open the partner's door to all of them. Before your rental the IP may have been used by someone else; see the [dedicated vs shared comparison](https://rackproxies.com/dedicated-vs-shared-proxies/).

### Can I use one IP for several partner APIs?

Yes. One rented IP can be added to as many allowlists as you need, and every tool you route through it shares that exit. Many teams still use two IPs so one renewal or replacement never cuts every integration at once. 5 IPs costs $6.45.

### Can my CI pipeline use the static IP?

Yes. Store the proxy line as a secret and set it as `HTTPS_PROXY` in the job. Use the username and password, because CI runners change address. HTTP, HTTPS (CONNECT) and SOCKS5 are supported, so most build tools and package managers work through it.

### Which country should the IP be in?

Choose a country close to the API's servers to keep the round trip short, unless the partner requires a specific country. For an API hosted in Virginia, an IP in [Ashburn](https://rackproxies.com/datacenter-proxies/united-states/ashburn/) or [New York](https://rackproxies.com/datacenter-proxies/united-states/new-york/) adds little distance. Availability varies; the checkout shows what is online.

### Will I keep the same IP next month?

Renew from your account 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. Give your partner a second IP as a backup if downtime would hurt.

### Do I need ID to rent a static IP?

No KYC: no ID, no selfie, no documents to sign up, top up or buy. You pay in BTC, USDT, USDC, ETH, SOL, LTC and log in with an account number. Some partners ask who owns an address; you can explain that it is a rented datacenter IP and show the [sourcing page](https://rackproxies.com/sourcing/).

---

RackProxies: RackProxies is a dedicated datacenter proxy provider: IPv4 addresses rented per IP for 30 days, paid in crypto with no ID upload. Pages cover 22 countries and 34 datacenter cities with public network data.