Sub-users
A sub-user is a separate proxy login on your traffic, with its own password and an optional GB limit. Give one to each project, server or teammate.
- Where
- Sub-users tab of the Residential or Mobile page
- How many
- Up to 50 per product
- Traffic
- From the product's pool, with or without a cap of its own
- Through the API
- Sub-users API
When to use one
- To count traffic per project or per script, and stop one without touching the others.
- To change one password without breaking every tool.
- To give a colleague proxy access without sharing your dashboard login.
Sub-users are for your own organization: your team, projects and apps. Giving them to people outside it counts as resale, which the Terms of Service allow only with our written consent.
Create a sub-user
- Open Residential or Mobile, then the Sub-users tab. A sub-user belongs to one product.
- Press Add user.
- Name: lowercase letters, digits and dashes, for example
scraper-eu. Capitals become lowercase and other characters turn into dashes. Each name is used once per product. - Traffic limit: the GB it may use from this product's pool.
0means no limit of its own: it can use everything the pool has. - Press Create user. The new row shows its login, with a copy button.
Its password
A new sub-user gets a random password, and the list shows logins only. To see a password, press the gear icon on the row, then New password: the dialog shows the new password with a copy button until you close it, and the earlier one stops working at once. Do it right after Create user, before any tool uses the login. Through the API, List sub-users returns each login with its current password.
Use it
A sub-user login takes the same targeting and session keys as the main login, on gate.aeonproxy.com port 7000 (HTTP) or 7001 (SOCKS5): LOGIN-cc-de-sid-ab12cd34-ttl-30 with the sub-user's login as LOGIN and its own password. The dashboard generator writes lines for the main login, so swap the login at the start of each line, or call Generate a proxy list with sub_user_id.
Limits, usage and removal
- Each row shows “X of Y GB used” with a bar, or ∞ without a limit.
- At its limit a sub-user turns to Limit reached and the gateway answers 402 for its login. Raise the limit in the gear dialog and press Save to let it work again.
- A limit cannot be larger than the product's total traffic; a larger value is cut down to it.
- The Statistics tab shows the product's traffic; Include sub-users adds or removes their share. For one sub-user's figures, use the Usage API.
- Remove in the gear dialog deletes the sub-user, and its login stops working at once.
Questions
No. It uses your pool for that product. The limit is a cap on its share, not a separate purchase.
No. A sub-user is a proxy login and password only; it never sees your balance, orders or settings.
In the dashboard the gear dialog changes the limit and the password. To rename one, use Update a sub-user in the API; the login itself stays the same.