Sub-accounts

✓Residential — supported✓Rotating ISP — supported✓Rotating DC — supported

A sub-account is a second set of proxy credentials under your account. It has its own username, password and bandwidth allowance, and draws from your single billing relationship.

Use them to give a client, a team or one project credentials you can cap and revoke without touching anything else.

Creating one

Open your product, go to Proxy Access, and select the Sub-accounts tab. From there you create the sub-account, assign it bandwidth, and see its usage.

Each has its own detail page with its credentials and a bandwidth chart, so you can attribute consumption without running separate accounts.

Note

Sub-accounts become available after your first purchase. On a trial you will only see the master credentials.

Master versus sub

Master credentials bill straight to the account and are not capped by any sub-account limit.

Sub-account credentials are capped at whatever you assigned. When a sub-account runs out its requests stop, and the rest of your account carries on unaffected. That containment is the point: a client who burns their allowance cannot spend yours.

Not available on the Scraping API

The Scraping API uses a single token per account. If you need separated credentials and per-user limits, that is a proxy product feature.

Whitelists are per sub-account

Each sub-account keeps its own IP whitelist. Whitelisting an address on the master account does not authorize it for a sub-account.