Skip to main content

​
Error reference

On validation failures the message field is an array of strings, not a single string. Handle both shapes when parsing errors.

​
Retries

502 responses are always safe to retry. Creation and top-ups are atomic: on any failure, nothing is charged and no sub-user is left half-created. You will not double-spend your pool by retrying. Other statuses are not transient — retrying a 400 or 409 with the same body returns the same error.

​
Suspended accounts

If every call starts returning 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 immediately, but you can’t create or top up accounts while suspended.

​
Sub-user lifecycle

Sub-users cannot be deleted or paused. An account works until its data is consumed, and data assigned to a sub-user cannot be moved back to your pool.
Assign conservatively and top up as needed, rather than front-loading a large allocation you can’t reclaim.

​
Usage etiquette

Usage lookups hit the gateway live. Fetch them when you actually need them — page loads, billing runs — rather than in tight polling loops. On GET /reseller/users, includeUsage=true costs one gateway lookup per row, so it’s the request most worth keeping out of a loop. Questions? Contact your Roundproxies account manager or email team@roundproxies.com.