Sub-accounts
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.
A sub-account is on the same product and tier as the login it belongs to, and it cannot be set to a different one.
Creating one
Section titled “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.
Master versus sub
Section titled “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.
Scale sub-accounts
Section titled “Scale sub-accounts”On Scale Residential, Scale Rotating ISP and Scale Rotating DC a sub-account is a second login on the same package. Its traffic counts against your package the same way your own login’s does.
A sub-account limit does not buy extra traffic. It sets how much of your package that sub-account may spend before it is stopped on its own, and a sub-account with no limit is never stopped for a limit of its own. Limits run over a window you choose: total, daily, weekly or monthly. The daily, weekly and monthly ones reset on the calendar.
Create, limit, stop and delete them under Proxy Access → Sub-accounts. Deleting one is immediate and cannot be undone, and traffic it already used stays on that month’s usage.
Not available on the Scraping API
Section titled “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
Section titled “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. Scale logins have no IP whitelist.
Was this page helpful?
Thanks. That helps us fix it.