Proxy-seller

Subaccounts (subusers)

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

GET/residentsubuser/packages
Get package information
All subuser packages with traffic limits, expiration, and package keys.

Write

POST/residentsubuser/create
Create subuser package
Reserve traffic and a validity period from your main tariff for a new subpackage.
POST/residentsubuser/update
Update package
Adjust traffic allocation, rotation, or validity. Unused traffic stays in the subpackage.
DELETE/residentsubuser/delete
Delete subuser's package
Remove the subpackage. Any unused traffic returns to your main tariff.

Lists in subuser package

same operations as parent residential lists, scoped to a subpackage

Read

GET/residentsubuser/lists
Retrieve existing IP lists
All lists in a subpackage. Filter by `package_key` or `listId`.

Write

POST/residentsubuser/list/add
Create IP list
Add a list to a subpackage with GEO filter and auth method.
POST/residentsubuser/list/rename
Rename created list
Change the list's display name within a subpackage.
POST/residentsubuser/list/rotation
Change rotation
Set sticky, per-request, or time-based rotation (1–3600 seconds).
DELETE/residentsubuser/list/delete
Delete list
Remove a list from a subpackage. Active connections drop within ~60 seconds.

Special: API-TOOL list

Common to all subaccount endpoints

  1. Base URL

    https://proxy-seller.com/personal/api/v1/{YourApiKey}/residentsubuser/
  2. Authentication

    API key in URL path (your main account key, not the subuser's)

  3. Required parameter

    Most endpoints require package_key — get it from

    GET/residentsubuser/packages
  4. Error model

    Business errors return HTTP 200 with errors[] populated

Residential proxysame operations on your main packageOpenSession ID + TTLpin sessions for subuser listsOpenCases (FAQ)common subuser scenariosOpen

FAQ

On this page