Creating Sub Account

Learn how to create and manage sub-accounts for Rapidproxy dynamic residential proxies using username and password authentication.

This guide explains how to create a sub-account for Dynamic (Rotating) Residential Proxies using username and password authentication in Rapidproxy.

Sub-accounts allow you to manage proxy access, credentials, and traffic limits separately for different applications, users, or environments.


What Is a Sub-Account?

A sub-account is an additional proxy credential under your main Rapidproxy account.

With sub-accounts, you can:

  • Use username & password authentication instead of IP whitelisting

  • Assign separate credentials for different projects or team members

  • Set a traffic cap (GB) to control bandwidth usage

  • Enable or disable access without affecting the main account

Sub-accounts are commonly used when multiple services or users need independent proxy access.


How to Access the Sub-Account List

To locate the Sub-account management page in the updated dashboard:

  1. Log in to your Rapidproxy account.

  2. Go to UCenter.

  3. Navigate to: Proxies → Rotating Residential Proxies → Use Proxy → Sub-account list

This page displays all existing sub-accounts under your main account.


Creating a New Sub-Account

Follow these steps to create a new sub-account:

  1. On the Sub-account list page, click the Add button.

  1. Fill in the required fields:

  • Username – the proxy username for this sub-account

  • Password – the proxy password

  • Traffic cap (GB) – maximum traffic allowed for this sub-account

  1. Set the account Status to Enabled / Active.

  1. Click Confirm to save the sub-account.

Once saved, the sub-account becomes available for proxy authentication immediately.


Traffic Cap Behavior

The Traffic cap (GB) limits how much bandwidth the sub-account can use.

  • Traffic usage is deducted from your main account balance

  • When the traffic cap is reached, the sub-account will stop working

  • You can update or increase the traffic cap at any time from the sub-account list

This feature helps prevent unexpected usage and allows better traffic control per project.


Using the Sub-Account

After creating a sub-account:

  • Use the Username and Password as proxy authentication credentials

  • Configure your application, browser, or script with these credentials

  • No IP whitelisting is required when using username/password authentication

Each sub-account operates independently while sharing the main account’s purchased traffic.


Managing Sub-Accounts

From the Sub-account list, you can:

  • Enable or disable a sub-account

  • Edit username, password, or traffic cap

  • Remove sub-accounts that are no longer needed

All changes take effect immediately after saving.


When to Use Sub-Accounts

Sub-accounts are recommended if:

  • You manage multiple applications or environments

  • You want to assign separate credentials to different users

  • Your IP address changes frequently

  • You prefer credential-based authentication over IP whitelisting


Need Help?

If you have questions about sub-accounts or authentication methods:

Support can assist with configuration and usage questions.

Last updated