Capabilities & scope

These features use the same ARNPROXY account and existing website workflows. Required permissions, eligible products and verification rules are documented on each operation page.

Account and balance

Read account details, currency, balance and effective permissions. A key is provisioned on the first eligible account-page visit; administrator restrictions and verification rules remain in force.

Purchases and multi-country orders

Use up to 20 distinct location_id values under one product_id. Each country creates a separate order record; the linked checkout is handled as one invoice. Quantity discounts are calculated independently per country.

Accepted does not mean delivered

HTTP 201/202 or state=accepted may confirm acceptance only. Follow the same operation with purchase_status / residential_purchase_status and fulfillment with order_delivery. Honor poll_after_seconds and Retry-After when present. Do not repurchase under a new Idempotency-Key after a timeout.

Active proxies, notes and export

Read only your own active proxies and order connections. Manage notes and export connection details or CSV/custom content with the required permission. Other customers’ data is not exposed.

Renewals and automatic renewal

Check renewable proxies and quotes, then renew from the balance. The automatic-renewal API manages the existing balance method; enabling it does not charge immediately or alter card-renewal settings.

IP replacement requests

Get a quote, submit a request and track it. Requests follow existing administrator review; they do not instantly assign a new IP for every call.

Extra logins separate from the primary

Create, list, replace and delete extra logins while preserving primary delivery credentials. Get random/custom modes and length rules from options. Some actions affect a package/order group. The account Logins page provides viewing and deletion; creation/replacement uses the API.

Proxy authorized-IP management

Use IP add/remove only as allowed by the scope/options response. Actions may be package-wide; do not omit scope acknowledgments. API removal is limited to your account’s recorded API-added IP grants.

Residential: new package versus GB top-up

Customers do not select a purpose for Residential orders. For a new package, the server automatically assigns the same fixed purpose as the website checkout; do not send purpose_id, subpurpose_id or other_purpose. A top-up preserves the existing package purpose.

Locations, IP pool and connection lists

Read country/region/city/ISP choices and IP-pool observations. Create lists, change their title/rotation or delete them. Select supported login/password or IP authentication when creating a list. Pool counts may be cached observations, not an IP guarantee for every connection.

Sessions & targeting

Create and verify an eligible special Residential list first, then prepare session/TTL connection strings. Formatting a connection does not consume traffic; actual use does.

Rotating proxies

Set the IP-change interval in seconds for an eligible Rotating package. This is not an instant IP-swap action; the setting applies at package scope.

Two separate IP allowlists

The allowlist in My account → API controls which addresses may use the API key and is managed on the account page. Proxy authorized-IP operations control which addresses may connect to the proxy. These settings do not modify one another.

Webhooks and ready-made clients

Webhooks are optional. Use your own HTTPS receiver and verify signatures, or follow results with status requests. PHP, Python, Node.js, Java and Go SDKs and Postman collections are available.

Webhook · SDK / Postman

Unavailable operations and important limits

Permissions come from administrator account settings; customers do not select additional scopes. Existing administrator restrictions apply.

Usage purpose: select only the subpurpose