Subaccounts (subusers)
Updated:
Provision subuser packages and manage their lists — without sharing your main credentials.
A subuser package is a child subscription carved out of your main residential package. You allocate a slice of traffic and a validity period to it, and the subuser manages their own lists inside.
Use this for resellers, team members, or isolated client environments. Traffic spent in the subpackage is reserved from your main quota; on deletion, unused traffic returns to the parent.
Subuser package
create, configure, and remove subpackages
Read
Write
Lists in subuser package
same operations as parent residential lists, scoped to a subpackage
Read
Write
Special: API-TOOL list
Common to all subaccount endpoints
Base URL
https://proxy-seller.com/personal/api/v1/{YourApiKey}/residentsubuser/Authentication
API key in URL path (your main account key, not the subuser's)
Required parameter
Most endpoints require package_key — get it from
GET/residentsubuser/packagesError model
Business errors return HTTP 200 with errors[] populated
Related
Residential proxysame operations on your main packageOpenSession ID + TTLpin sessions for subuser listsOpenCases (FAQ)common subuser scenariosOpenFAQ
No — the naming is misleading. In this API a "subuser" is a sub-package: a slice of your main residential package with its own traffic_limit, expired_at, is_active toggle, and lists.
All /residentsubuser/... endpoints take {YourApiKey} — your own. There is no second API key issued anywhere in the spec. The credentials your end-user receives are list-level login/password (returned by /residentsubuser/list/add) — those are connection credentials for the proxy, not management keys.
No. The subuser sees only its own traffic_limit and consumed. The main account sees both layers.
Call update-package with an increased traffic_limit. The top-up is applied immediately.
No. Lists are bound to the subpackage they were created in. Recreate the list under the target subuser.