datacenter (shared IPs) and isp (dedicated IPs). Instead of a pool of GB, you have a capacity limit for each product, for example 100 datacenter and 20 ISP IPs at the same time. You take an allocation, a batch of IPs for one customer, and release it when the customer leaves.
Unlike the residential pool, this limit is enforced. Check
limit and used in GET /reseller/account before asking for a large batch. To raise a limit, contact your account manager.
To see which regions are available and how many IPs they have, use the public
GET /region/availability?type=... endpoint.
Allocate Proxies
POST /reseller/proxies
- Node.js
- Python
- cURL
Node.js
Request Parameters
Response
Response
Errors
Not enough capacity or IPs (400)
Not enough capacity or IPs (400)
You asked for more than your limit allows, or a region doesn’t have enough IPs. Nothing is assigned. Release an allocation, ask for fewer IPs, or request a higher limit.
Allocation failed (502)
Allocation failed (502)
Nothing is assigned. You can safely retry.
List Allocations
GET /reseller/proxies
Lists your allocations page by page. The IP lists are not included here. Get a single allocation for those.
- Node.js
- Python
- cURL
Node.js
Query Parameters
Get One Allocation
GET /reseller/proxies/:id
Returns the allocation and its full list of IPs with credentials. Released allocations are still returned, with an empty proxies list.
- Node.js
- Python
- cURL
Node.js
Release an Allocation
DELETE /reseller/proxies/:id
Removes all IPs in the allocation and returns the capacity to you.
- Node.js
- Python
- cURL
Node.js
Errors
Already released (400)
Already released (400)
The allocation was released before. Nothing to do.
Limits
- Batch size: at most 1000 IPs per allocation.
- Capacity: the total IPs in your active allocations can’t go over your
limitfor each product. - Released IPs: can’t be brought back. A new allocation gives different IPs.
Related
Proxy Access
How your customers use the IPs you allocate.
Basics
Check your capacity and pool with
GET /reseller/account.