# Buy and manage a mobile proxy

Choose an available duration, copy connection details and use the controls supported by your proxy.

2026-10-14 · SMS.Red

## Choose a proxy license

The public Proxies page shows current duration prices beside an order summary. Its coverage explorer searches the states listed for the selected plan; change duration to compare coverage. City-level location selection is available in your dashboard after activation. The protocol preview is illustrative and contains no usable credentials.

The duration selected on the pricing page is carried into checkout. If plans fail to load, use Retry; unavailable plans cannot be purchased. Review the wallet total and pay once. If a request times out, retry the same action: its saved request key prevents a duplicate charge. Keep any Paid or Provisioning order while the result is checked.

Browse the locations for the selected plan before paying. After activation, filter by city, state or carrier and choose the location in your dashboard. Network variants share one state filter. Listings can change; connection confirms availability.

## Connect and copy updated credentials

Search or filter locations and choose a supported location. Connecting changes the IP and password, so copy the updated details afterwards. The selected license shows IP, port, username, password and HTTP/SOCKS5 quick-connect strings. Use the protocol and exact port shown by the interface.

Keep credentials private and update your client whenever they change. A saved old password can cause authentication failures after switching location.

## Disconnect, reset, fingerprint and renew

Available controls depend on the selected proxy. Renewal, disconnect, hard reset and TCP fingerprints are shown only where supported. A proxy without renewal ends at expiry; a new purchase provides a new connection.

Disconnect stops the current connection. Fast reset and Hard reset request their respective supplier reset modes; wait for the action result and check current details before reconnecting your client. Do not assume resets preserve every credential.

Renewal shows its current price and is available only before expiry. A pending renewal disables another renewal. Wait for confirmation, then check the new expiry. Renewing a disconnected proxy keeps it disconnected. A confirmed rejection returns the charge to your wallet; an uncertain result remains pending for reconciliation.

## API and lifecycle webhooks

Include the offerKey from the current product catalog with pricingCode at purchase. If the offer changes, refresh before paying. Read capabilities and socks5Port from proxy details; use the explicit port. Add pricingCode to the proxy-locations query when choosing an initial location for a plan. Persist an Idempotency-Key for connect and reset as well as paid actions.

Create an API key in Developers. Use /api/v1/developer/proxy-products and /proxy-locations to browse, then POST /proxies with pricingCode and a saved Idempotency-Key. Reuse that key after a timeout or GET /proxy-requests/{key}. List, details, connect, disconnect, reset, fingerprint and renew use /proxies/{id}. New webhooks can subscribe to proxy.ready, proxy.updated, proxy.renewed, proxy.renewal_failed, proxy.failed and proxy.expired. See the [proxy API reference](https://sms.red/docs/ai/proxies.md).