Error Handling

Errors

Status	Where	Example message	What to do
`400`	anywhere	Validation errors. `message` is a list of strings	Fix the request body
`400`	`POST /reseller/users/:username/data`	Removing more data than the account has, or an amount of zero	Change the amount. An account’s data can’t go below zero
`400`	`POST /reseller/proxies`	Not enough capacity, or not enough IPs in a region	Release an allocation, ask for fewer IPs, or request a higher limit
`400`	`DELETE /reseller/proxies/:id`	Allocation already released	Nothing to do
`400`	usage history	The range is longer than allowed for that granularity	Use a shorter range or a larger granularity
`401`	reseller endpoints	`Invalid reseller API key`	Check the key, or rotate it with `POST /reseller/self/rotate-key`
`401`	reseller endpoints	`Reseller account is suspended`	Contact support
`403`	`POST /reseller/self/rotate-key`	The reseller account is suspended	Contact support
`404`	`GET /reseller/self`	The logged-in user has no reseller access	Request access
`404`	sub-user endpoints	`Sub-user "x" not found`	Check the username. You can only see your own sub-users
`409`	`POST /reseller/users`	`Username "x" is already taken. Pick another one.`	Choose a different username
`502`	anywhere	Message ends with `Nothing was charged` and asks you to retry	Retry. Nothing was changed

For validation errors, message is a list of strings, not a single string. Handle both when you read errors.

There Is No “Not Enough Data” Error

The residential pool is tracked, not enforced. Creating or topping up a sub-user never fails because you are out of data. remainingBytes just goes negative. Keep an eye on it and buy more residential data when it drops below zero. Static proxy capacity works the other way: it is enforced, and asking for more than you have returns 400 with nothing assigned.

Retries

You can always retry a 502. Creating sub-users, changing their data, deleting them and allocating proxies either fully succeed or change nothing.

A 502 on POST /reseller/users means no account was created and no data was taken.
A 502 on DELETE /reseller/users/:username means the sub-user is unchanged. The credentials still work and nothing was refunded.
A 502 on POST /reseller/proxies means no IPs were assigned and no capacity was used.

Other errors don’t go away on their own. Retrying a 400, 404 or 409 with the same request gives the same error.

Suspended Accounts

If every call returns 401 Reseller account is suspended, contact support. Your existing sub-users keep working until their data runs out, so your customers aren’t cut off right away. While suspended, you can’t create, change or allocate anything.

Deleting Sub-Users

You can delete sub-users. Their unused data returns to your pool, the same as when you remove data from an account. Data your customer already used is gone.

You can’t undo a deletion, and the account’s data is removed first. To give a customer access again, create a new sub-user with a new username.

Using Live Usage Sparingly

Live usage lookups contact the proxy network. Use them when you need them, such as page loads or billing runs, not in fast polling loops:

includeUsage=true on GET /reseller/users looks up every row.
includeUsage=true on GET /reseller/account looks up every sub-user.
live=true on usage history looks up every account in the range.

Without these options, usage history comes from stored data and is fast. Use it for dashboards and trends. Questions? Contact your account manager or email team@roundproxies.com.

Getting Started

Residential Proxies

ISP Proxies

Datacenter Proxies

Reseller

Errors

There Is No “Not Enough Data” Error

Retries

Suspended Accounts

Deleting Sub-Users

Using Live Usage Sparingly