Documentation | IPROAM

Overview

IPROAM provides three primary proxy products: Dynamic Residential, Dynamic Mobile, and Tunnel Proxy. The typical workflow involves creating and verifying an account, recharging or selecting a plan, purchasing access, configuring your client, testing with a small request, and monitoring usage.

Service scope: The service is only for lawful overseas-network scenarios. It is unavailable for use within mainland China and does not support cross-border networking.

Quick start

Create and verify your account
Register using email verification. You may also link Google sign-in from Account Security.
Recharge or select a plan
Add balance using Alipay or WeChat Pay, or select a specific product plan directly.
Purchase proxy resources
Buy traffic lots, mobile traffic, or tunnel instances depending on your use case.
Configure access
Use the dashboard generator to create your proxy endpoint string. Choose country, rotation, and protocol format.
Test with a small request
Run a minimal curl command to verify authentication and exit IP before running heavy tasks.
Monitor usage
Check the dashboard for aggregated traffic totals and lot expiry details.

Account

Registration and Google sign-in

Account registration requires email verification. Google sign-in can create a new account or link to an existing account through password verification or an email verification code.

An already logged-in customer can link or unlink Google in Account Security without re-entering their current password.
If Google is the only login method, you must set a local password through password reset before unlinking Google.
Password changes rotate the current session and sign out other old sessions.

Security notice: Never send passwords, proxy credentials, private keys, verification codes, or full payment credentials to support.

Balance, currency, recharge, and checkout

Ledgers and display currency

Your account has a single CNY cash ledger. The dashboard can display values in CNY or USD. Simplified Chinese browser preferences default to CNY; other languages default to USD. You can switch currency display in the dashboard.

USD is a display and recharge-input currency, not a second wallet. USD recharge is converted to CNY using a short-lived server exchange-rate snapshot. A conversion margin may apply. The checkout page or payment provider shows the final CNY amount before authorization.

Checkout and payment methods

Existing account cash balance is not a withdrawable cash account and is subject to Terms of Service.

Supported methods: Alipay desktop web checkout and WeChat Pay Native QR.
Pending expiry: Pending-payment expiry is shown on the payment/order record. You can continue an unexpired pending payment from its record.
Balance application: At plan checkout, using account balance is optional. If selected and insufficient, the balance portion is reserved and the external provider charges the remaining CNY amount. You can also choose full external payment even when balance is sufficient.
Coupons: Validated at checkout. The order locks the displayed price/discount/payment amount when created.

Invoices and refunds

You can view transaction and order records in the dashboard. We do not promise automated invoices or receipts; customers needing formal billing documentation should contact support before purchasing to confirm availability.

Paid digital proxy resources are generally not automatically refundable. See Section 4 of the Terms for actual refund terms. Contact support for duplicate charges, failed provisioning, or material billing errors.

Orders

Orders track plan purchases, recharges, and tunnel provisioning. If a payment fails or is interrupted, do not create repeated payments blindly. Reopen the unexpired payment from your dashboard order record. If the provider shows a success but the dashboard does not reflect it, check the provider result and contact support with the order/recharge ID.

Dynamic Residential

Dynamic Residential traffic is billed and backed by a shared residential traffic balance. The dashboard generator supports HTTP, SOCKS5, and SOCKS5H output. HTTPS destinations can be accessed through an HTTP proxy using CONNECT; do not call HTTPS a separate proxy endpoint.

Generator options

Country: The token Rand means random/global selection. Other country codes are lowercase ISO alpha-2 in actual generated usernames.
Rotation: Per-request rotation or timed rotation.
Output format & separator: Choose format and delimiter for copying multiple lines.

Timed rotation (Session)

Timed mode adds sessid and sesstime to the generated username. Reusing the same sessid attempts to keep the same exit until rotation, but carrier/pool/network changes mean it is not an absolute IP guarantee.

Example request

The panel generates the real endpoint. Copy your actual generated line from the dashboard. The example below uses synthetic credentials.

curl -x 'http://customer-YOUR_USERNAME-cc-us-sessid-demo123-sesstime-5:YOUR_PASSWORD@proxy.example.com:9000' https://api.ipify.org

There is no public control API documentation in this release; this documentation covers customer-visible proxy endpoints only.

Dynamic Mobile

Dynamic Mobile uses real mobile-network exits and shares the same generator workflow and protocol/output controls as Residential. It has an independent mobile traffic balance and independent traffic lots.

Availability: Mobile carrier availability, latency, IP continuity, and exact geolocation may vary. IPROAM does not promise a particular carrier, IP, precise city, latency, success rate, or uninterrupted availability.

Use the same safe test pattern as Residential. For lot details, see Traffic & validity.

Proxy Parameters

Dynamic Residential and Dynamic Mobile usernames use the same parameters. This section describes each parameter and the two rotation modes.

country

Rand selects a random exit worldwide. Any other value must be a lowercase ISO 3166-1 alpha-2 country code (for example us), which selects an exit IP in that country.

sessid

Present only in timed rotation mode. A session identifier of 1–24 ASCII letters, digits, or underscores. Reusing the same sessid attempts to keep the same exit, but a sticky exit is not guaranteed.

sesstime

Present only in timed rotation mode. The session duration in minutes; the valid range is 1–30. After this time, the exit may rotate.

Rotation modes

Per-request: The username omits sessid and sesstime. A fresh session is selected on every request.
Timed: The username includes sessid and sesstime. The same session is kept where possible until the session time elapses.

Tunnel Proxy

Tunnel Proxy offers two billing modes: Quantity billing and Traffic billing. Both support country and rotation controls.

Quantity billing

Purchasing immediately starts provisioning the requested tunnels.
There is no unused tunnel quota to manually consume later.
Each tunnel has its own endpoint/port.
Traffic is unlimited for billing purposes, while usage can still be shown for visibility.
Service is validity based. Eligible quantity tunnels can be renewed from the dashboard when the renewal action is available; renewal is not automatic.

Traffic billing

Multiple active tunnels share the tunnel traffic balance.
Creating a tunnel does not reserve or pre-deduct a fixed GB amount.
Active tunnel count is limited by the value shown in your dashboard/plan, which may vary by account.
The tunnel endpoint/port persists.
When all shared traffic is consumed or expired, delivery is temporarily unavailable/depleted.
Adding valid tunnel traffic restores eligible existing tunnels without reallocating the endpoint.

Authentication

Authentication supports username/password or an IP/CIDR allowlist. An allowlist should contain only trusted public egress IPs, one IP or CIDR per line. Private LAN addresses normally will not match the public source seen by the service.

Tunnel states

Provisioning: The system is starting the tunnel. Provisioning may retry after temporary capacity or route unavailability. The order shows progress/reason.
Active: The tunnel is running and ready for use.
Suspended/Paused: The tunnel is temporarily inactive due to account or administrative action.
Expired: The validity period has ended. Quantity tunnels can be renewed if the dashboard offers the action.
Depleted: Traffic-billed tunnels pause when shared traffic is exhausted. Restored through shared traffic purchase, not quantity renewal.
Closed: Terminal state. The tunnel cannot be restored.

Use the export/copy controls in the dashboard to test the assigned endpoint without publishing real infrastructure.

Traffic lots and validity

Residential, Mobile, and Tunnel traffic are three independent balances; buying one never increases another.

Every purchased traffic package is a separate lot with purchased, used, remaining, source, and expiry information.
Consumption uses the valid traffic lot that expires first.
When a lot expires, unused traffic in that lot is no longer available. Buying a new package does not extend older lots unless explicitly stated.
Historical migrated balance can appear as long-term legacy traffic. Do not assume all traffic is permanent.
Customer-visible complimentary or compensation traffic has the validity shown in its lot details.

Usage and records

The dashboard shows totals, remaining traffic, traffic-lot detail, and aggregated usage charts/records. Usage data is aggregated and can have a short reporting delay.

Quantity-billed tunnel usage may be measured/displayed but does not deduct a traffic balance.

Overhead differences: Proxy response bytes and site/app-level payload calculations may differ because of protocol overhead, retries, compression, and reporting boundaries.

Troubleshooting

Symptom	Possible Cause	Action
No response or timeout	Bad endpoint, protocol mismatch, invalid credentials, low balance/validity, allowlist mismatch, destination unavailable.	Verify generated line, protocol, credentials, and balance. Check allowlist public egress IP. Test a small HTTPS IP-check request.
Authentication failure	Outdated generated line, special characters not URL-encoded, wrong country/session parameters, allowlist mode vs credentials mode.	Copy the latest generated line. URL-encode credentials in custom code. Verify auth mode matches panel config.
IP changes too early or does not change	Mismatch between per-request and timed rotation settings.	Distinguish per-request vs timed rotation. Understand timed mode is best-effort session continuity, not an absolute IP guarantee.
Desired country unavailable	Dynamic pool availability.	Select another country or the global/random option. Retry later.
Traffic appears depleted	Checked wrong product balance, or lot expired.	Check the correct product balance and lot expiry. Purchase that product's traffic if needed.
Payment pending/expired/paid but not reflected	Checkout interrupted, provider delay, or expired pending window.	Do not create repeated payments. Reopen unexpired payment from records. If paid but not reflected, contact support with order ID.
Tunnel provisioning delayed	Temporary route or capacity unavailability.	Check progress/reason in the order. Wait for automatic retry. Contact support if persistent.
Tunnel unavailable	Expired quantity tunnel, depleted traffic tunnel, suspended, closed, or credential/allowlist error.	Distinguish state in dashboard. Renew quantity tunnels or add traffic for traffic-billed tunnels. Verify auth settings.

Security, compliance, support

Security best practices

Use HTTPS destinations when possible.
Keep credentials out of source repositories and logs.
Rotate exposed credentials immediately.
Use the narrowest safe allowlist for IP/CIDR authentication.

Compliance

Follow destination terms and applicable law. No unauthorized access, credential attacks, fraud, spam, malware, denial of service, unlawful scraping, or attempts to bypass controls. See Terms and Privacy. This documentation is operational guidance and does not replace them.

Support

For help, contact support@iproam.com. A useful support request includes:

Account email
Product (Residential, Mobile, Tunnel)
Order/recharge/tunnel ID
Timestamp and time zone
Client/protocol
Sanitized error message
Destination hostname
Minimal sanitized reproduction steps

Before sending screenshots/logs: Remove passwords, full proxy URLs, verification codes, payment credentials, cookies, and private keys.