Basics

The Reseller API covers two product lines:

Residential data — a pool of GB, measured against your own residential purchases. You spend it by creating sub-users: username/password accounts on our residential gateway, each with its own traffic limit, which you hand to your customers.
Static proxies — datacenter (shared IPs) and ISP (dedicated IPs). You hold a concurrent capacity limit per product and draw allocations of IPs against it.

Your customers never need to touch this API. They just use the proxy credentials you give them.


Base URL	`https://api.roundproxies.com`
Format	JSON in, JSON out

Send Content-Type: application/json on every request that has a body.

Everything below can also be done from your reseller dashboard. The API exists so you can automate it from your own systems.

Where your data pool comes from

Your residential allocation is self-funding: it is your own purchased residential data, plus any optional top-ups we grant you.

allocatedBytes = purchasedBytes + grantedBytes
remainingBytes = allocatedBytes − assignedBytes

purchasedBytes — residential data you bought through the dashboard like any other customer. Kept in sync automatically; buy more and your reseller allocation grows with it.
grantedBytes — optional manual top-ups from us (compensation, negotiated bonuses). Not required for the pool to work.

The pool is tracked, not enforced. Creating a sub-user never fails for lack of data — remainingBytes simply goes negative, recording how far ahead of your purchases you’ve assigned. There is no “not enough data” error.

A negative remainingBytes is your signal to buy more residential data. It is a bookkeeping figure, not a block — monitor it yourself.

Units

The API is asymmetric about units, and it’s the most common thing to get wrong:

Every data figure in responses is in bytes (dataBytes, remainingBytes, rawUsed).
Every data figure you send is in whole GB, where 1 GB = 1024³ bytes (1,073,741,824).

const BYTES_PER_GB = 1024 ** 3;
const toGB = (bytes) => (bytes / BYTES_PER_GB).toFixed(2);

Format displayed values from the raw byte fields with the 1024³ divisor, so a 2 GB account displays as “2.00 GB”.

Your account

GET /reseller/account

Returns your pool, where it came from, and your static proxy capacity.

cURL

curl https://api.roundproxies.com/reseller/account \
  -H "x-reseller-key: $KEY"

200 OK

{
  "account": {
    "id": "...",
    "name": "Acme",
    "email": "acme@example.com",
    "apiKeyPrefix": "rsl_a1b2c3d4",
    "data": {
      "allocatedBytes": 107374182400,
      "remainingBytes": 64424509440,
      "assignedBytes": 42949672960,
      "purchasedBytes": 96636764160,
      "grantedBytes": 10737418240
    },
    "proxies": {
      "datacenter": { "limit": 100, "used": 13 },
      "isp": { "limit": 20, "used": 0 }
    },
    "createdAt": "..."
  },
  "subUserCount": 8
}

Response Fields

Field	Type	Description
`account.apiKeyPrefix`	string	The visible prefix of your active key, for identifying which key is in use
`data.allocatedBytes`	number	`purchasedBytes + grantedBytes`
`data.purchasedBytes`	number	Your own residential-data purchases
`data.grantedBytes`	number	Manual top-ups granted to you
`data.assignedBytes`	number	Data currently assigned to sub-users
`data.remainingBytes`	number	`allocated − assigned`. Signed — goes negative when you over-assign
`proxies.<product>.limit`	number	Concurrent IPs you may hold for `datacenter` / `isp`
`proxies.<product>.used`	number	IPs currently held in active allocations
`subUserCount`	number	How many sub-users you’ve created

To increase your allocation, buy residential data from your dashboard. To raise your static proxy capacity, contact your account manager.

Live usage

Add includeUsage=true to fold in live consumption counters from the gateway:

cURL

curl "https://api.roundproxies.com/reseller/account?includeUsage=true" \
  -H "x-reseller-key: $KEY"

{
  "usage": { "rawUsed": 1288490188, "rawTotal": 6442450944, "failedLookups": 0 },
  "retailUsage": { "rawUsed": 0, "rawTotal": 5368709120 }
}

Field	Description
`usage`	Consumption summed across all your sub-users
`usage.failedLookups`	Sub-users whose gateway lookup failed. Their usage is excluded from the sums — treat any non-zero value as a partial total
`retailUsage`	Live counters for your own residential package (the source of the pool), kept separate so each used/total pair stays a sane ratio

retailUsage is null when the account has no retail package, or when its gateway lookup failed. Treat null as “unavailable”, never as zero.

includeUsage=true performs one gateway lookup per sub-user (batched), so it’s noticeably slower. Without the flag the endpoint makes no gateway calls at all. For trends over time use Usage History instead — it’s served from stored history and costs nothing.

Next steps

Authentication — your API key, dashboard-token access, and rotation
Sub-Users — create, list, adjust, and delete customer accounts
Static Proxies — allocate and release datacenter and ISP IPs
Usage History — consumption time series
Proxy Access — the gateway format your customers connect with
Error Handling — error reference and retry behavior

Getting Started

Residential Proxies

ISP Proxies

Datacenter Proxies

Reseller

Reseller API

Where your data pool comes from

Units

Your account

GET /reseller/account

Response Fields

Live usage

Next steps

​Where your data pool comes from

​Units

​Your account

​GET /reseller/account

​Response Fields

​Live usage

​Next steps

Where your data pool comes from

Units

Your account

GET /reseller/account

Response Fields

Live usage

Next steps