Refresh Static Datacenter Proxies

Refresh Static Proxies
GET /api/v1.0/datacenter/refresh-static

Creates a new customer-specific static proxy file and replaces the existing static allocation after a successful refresh.

The number of refreshed proxies is read from plan.static_proxies. It is not fixed to 2,000 by this endpoint.

A successful refresh starts a new 24-hour cooldown and returns the exact next available refresh time.

Rate
Maximum 4 requests every 60 seconds
Note
The X-API-Key header is accepted as an alternative to the apiKey query parameter.
Every response includes Cache-Control: no-store.
Required parameters
apiKey - query string
Endpoint details
Access requirements
Account status
The user account must have status ACTIVE.
Subscription type
The current plan type must be Datacenter.
Subscription status
Both active and canceled datacenter subscriptions are accepted while they remain usable.
Concurrency
The current datacenter plan must have a concurrency value greater than zero.
Static allocation
plan.static_proxies must contain a positive proxy amount, and the account must have an email address.
Response contract
Successful refresh - HTTP 200
Returns success, message, next_available_at, proxy_amount, proxy_file, and note. next_available_at uses the Europe/Berlin format HH:mm:ss dd.MM.yyyy.
Cooldown active - HTTP 200
The backend does not return an HTTP error while the cooldown is active. It returns: { "success": false, "message": "Static proxy refresh not yet available.", "next_available_at": "14:30:00 30.06.2026", "retry_after_seconds": 43120 }
Cooldown duration
The customer API refresh cooldown is 24 hours from the successful refresh time.
Replacement behavior
The utility recreates the customer proxy file. The previous allocation is replaced only after the refresh operation succeeds.
Possible API responses
400 Bad Request
Missing API key, missing user email, or no static proxies assigned to the plan.
401 Unauthorized
The supplied customer API key does not match a user.
403 Forbidden
Inactive account, non-datacenter plan, unusable subscription status, or no concurrency assigned.
409 Conflict
The refresh was already processed concurrently or the subscription changed during reservation.
429 Too Many Requests
More than four requests were made within 60 seconds. Use the Retry-After response header.
500 Internal Server Error
Database access or proxy-file creation failed. The backend attempts to restore the previous cooldown value when file creation fails.
Python • requests 
import json
import requests

endpoint = "https://proxytitan.com/api/v1.0/datacenter/refresh-static"
api_key = "xxx"

response = requests.get(
    endpoint,
    params={"apiKey": api_key},
    timeout=30
)

print("Status:", response.status_code)
print(
    json.dumps(
        response.json(),
        indent=2
    )
)
Replace xxx with your customer API key. Send it in the query string or the X-API-Key header. Do not send a GET request body.
Response (JSON)
Show example response
Click to reveal the successful JSON structure.
The proxy amount and filename are generated from the authenticated customer’s current subscription.