How to set up a mobile proxy

1. Buy bandwidth with your balance

Open Proxy setup and choose By bandwidth. Your account balance is money available to spend; it is separate from the GB remaining on your proxy key. Adding funds alone does not buy a bandwidth plan.

Expand Buy bandwidth, choose an amount and check the total and validity date. If your balance is too low, use Add funds, complete the payment, then return to Proxy setup. Choose Buy with balance and confirm the amount. A successful purchase creates your key or adds data to your existing one.

New bandwidth plans are valid for 30 days. An active plan’s purchase extends its expiry. Always use the date and remaining data shown in your dashboard when planning a job. If you bought a rental instead, select Dedicated mobile and use that rental’s connection details.

2. Choose your connection settings

In the connection section, choose the mobile pool and an available country. The mobile pool and the residential pool are different products: select mobile when you need carrier connectivity. Check the current country list before buying for a particular location because availability can change.

Choose the protocol your application supports. An HTTP proxy can be used for HTTPS destinations when the client supports tunnelling. SOCKS5 needs a client with SOCKS support. Copy the host and port from the generated settings; do not mix the HTTP port with a SOCKS connection.

For applications with separate fields, enter the proxy host, port, username and password separately. The username includes your routing settings. Keep the full generated username rather than trimming it to the account identifier.

3. Choose how the session behaves

Start with Sticky for a login, cart or other sequence of related requests. Reuse the same generated session for that flow. Every 10 min and Every 30 min request periodic rotation; those intervals are approximate. Hard pin asks for the strictest device pin available. Gateway default leaves the choice to the gateway.

A sticky session does not promise that a mobile carrier will keep the same public IP forever. A reconnect or device availability change can affect the connection. Generating more sessions also does not guarantee a different public IP for every session.

4. Copy and test the connection

Copy a complete URL from Proxy setup, then use it in your client. Start with a small request to a page you control or an IP-check endpoint you trust. Check the result before starting a large download or a long job; test traffic uses your allowance too.

For a terminal check, save the copied URL in a local environment variable called PROXY_URL. The following command requests response headers from a destination you replace with your own test page:

curl --proxy "$PROXY_URL" --connect-timeout 15 --max-time 30 --head https://YOUR-TEST-DOMAIN/

The proxy URL contains your credentials. Keep it out of public code and screenshots. For Python, Node.js and browser examples, see the proxy API reference. If the request fails, use the troubleshooting guide before changing several settings at once.