Proxy for API Requests: A Static IP for Scheduled Data Sync

Why scheduled API jobs need a fixed IP

APIs increasingly tie access to the caller's IP. Stripe lets you restrict a key to specific IPv4 addresses — the approach it suggests when 'your servers have fixed IP addresses' — and its advanced policies can block residential proxies, public proxies, VPNs and Tor. A job on a laptop, a serverless function or a rotating proxy has no fixed address to allowlist.

CI is no help here: GitHub advises against using the GitHub-hosted runner IP ranges as allowlists because there are so many of them, and recommends larger runners with static IP ranges or self-hosted runners instead.

Rate limits are often counted per IP too. GitHub's REST API allows 60 unauthenticated requests per hour per originating IP and tells you when to retry with retry-after or x-ratelimit-reset. Jobs behind one office or NAT address share that budget; a static datacenter IP per job keeps limits and allowlist entries separate.

• Stripe docs — API keys: access policies (IP addresses, residential proxies)
• GitHub docs — GitHub-hosted runners: IP addresses and allowlists
• GitHub docs — Rate limits for the REST API

Recommended setup for API sync

Scroll horizontally with the arrow keys to read all content.

The button below opens Static Datacenter Proxies with the AI and automation use case. Choose Region, Term, Protocol and Quantity (up to 100 IPs at a time) before you pay.

• Proxy302 console — Static Datacenter Proxies
• Stripe docs — API keys: access policies (IP addresses, residential proxies)

Which Proxy302 proxy to buy

Scroll horizontally with the arrow keys to read all content.

Prices in US dollars. Top up your wallet once and pay any line from it. Nothing renews automatically — renew in My assets to keep an IP.

• Proxy302 pricing

Set up a static IP for API jobs in 5 steps

1. Choose the IPs

   The button below opens Static Datacenter Proxies (Per IP and term) with the AI and automation use case. Pick the Region, choose a Term and set Protocol to HTTP. Set Quantity to the number of IPs you need (one for each job or API account, up to 100 at a time). Click Review cost and generate.

2. Allowlist the IP

   In My assets, note each IP and add it to the API's allowlist or access policy. Keep the old server IP until the first run succeeds.

3. Set the proxy for the job

   In My assets, Copy gives host:port:user:password. Store PROXY_URL = http://USER:PASS@HOST:PORT and the API token as secrets in your scheduler or CI.

4. Run the job on a schedule

   Use the code below from cron, Task Scheduler or CI. It pages through the API, honours Retry-After on 429 and stops on the first empty page.

   Expected result A line such as 'synced N rows from M pages', and the API sees the proxy's IP.

5. Renew before the term ends

   Auto-renew isn't available yet, so renew the IP in My assets before it expires to keep the same address on the allowlist.

Paginated API sync through a static IP (Python httpx)

Scroll horizontally with the arrow keys to read all content.

# pip install httpx   then schedule it, e.g. cron:  */30 * * * *  python sync.py
import os
import time
import httpx

API = "https://api.example.com/v1/orders"
proxy = os.environ["PROXY_URL"]  # static datacenter IP: http://USER:PASS@HOST:PORT (allowlist this IP)
headers = {"Authorization": f"Bearer {os.environ['API_TOKEN']}"}

rows, page, waits = [], 1, 0
with httpx.Client(proxy=proxy, headers=headers, timeout=30) as client:
    while True:
        r = client.get(API, params={"page": page, "per_page": 100})
        if r.status_code == 429 and waits < 5:  # after 5 waits in a row, fail the run instead of looping
            waits += 1
            retry_after = r.headers.get("Retry-After", "")
            time.sleep(int(retry_after) if retry_after.isdigit() else 60)
            continue  # ask for the same page again
        r.raise_for_status()
        waits = 0
        batch = r.json()
        if not batch:
            break
        rows.extend(batch)
        page += 1
print(f"synced {len(rows)} rows from {page - 1} pages")

Checked on 2026-10-18 (httpx 0.28.1) against a local paginated API that answered 429 with Retry-After once: the job waited, re-requested the same page and synced all 5 rows from 3 pages; against an endpoint that kept answering 429 it gave up after five waits and exited with an error.

• Local proxy fixture run

Quick fixes

API proxy FAQ

Related setups

Uptime monitoring proxies

Uptime monitoring proxies: check your website from different countries on fixed datacenter IPs and alert only when two or more locations fail.

View options and pricing

AI agent proxies

AI agent proxy setup: give Browser Use, Playwright MCP and n8n agents their own exit IP — fixed datacenter IPs for tools and APIs, household IPs for browsing.

View options and pricing

Fast fixed IPs for APIs, tests and monitors

Fast datacenter proxies with fixed IPs, low latency and high concurrency — the lowest cost per IP for APIs, testing and bulk jobs. Pick the country; pay per IP and term.

View options and pricing