Generating Proxy Endpoints
Every field in the Endpoint Generator explained: protocol, proxy username and password, targeting, quantity, the results table and the per-row actions.
Last updated
The Endpoint Generator is the Configuration tab on an active product page, and it is the tool you will use most. It turns your traffic into concrete proxy endpoints you can paste into anything.
Reach it by opening a product under My Products and selecting the Configuration tab.
The form
| Field | What it does |
|---|---|
| Protocol | Which proxy protocol the generated endpoint speaks |
| Proxy username | Which sub-user the credentials belong to |
| Proxy password | The secret for that sub-user |
| Proxy format | How the endpoint string is written when you copy it |
Protocol
Three options.
| Protocol | Use it when |
|---|---|
| HTTP | The target or tool expects an HTTP proxy |
| HTTPS | You need a tunnel for encrypted traffic |
| SOCKS5 | The client requires SOCKS5, common for browser and network-level tools |
If you are unsure, HTTP is the most widely accepted. The choice only affects the string the generator writes and the code snippets; the same traffic works either way.
Proxy username
This is the sub-user the endpoint will authenticate as. Selecting it loads that sub-user's credentials.
Two things worth knowing:
- A sub-user that is still being provisioned appears in the list but is disabled, so it cannot be selected until it is ready.
- If the list is empty, there are no sub-users yet. The generator says so and links you toward creating one, described in Sub-users.
Proxy password
The secret for the selected sub-user. It is fetched on demand and shown so the generated strings are copy-ready. Revealing it is an owner-only action.
Advanced settings
Country, Region and City narrow where your requests appear to originate.
| Field | What it narrows |
|---|---|
| Country | The country the exit address is registered in |
| Region | The state, province or region within that country |
| City | The city within that region |
Each level down narrows the pool of available addresses. Country targeting almost always succeeds; city targeting succeeds less often and may be slower, because fewer addresses match. Target as narrowly as your task genuinely needs and no narrower.
The targeting fields are covered in more detail in Geo-Targeting.
Generating
- Choose the Protocol.
- Choose the Proxy username.
- Optionally set Country, Region and City.
- Set Proxies quantity to how many endpoints you want, from 1 to 10.
- Select the generate action.
The generator produces that many endpoints, each with its own session, and writes them into the results table below.
The results table
Two view modes, switched with Table and List.
Table shows one row per endpoint split into columns: Hostname, Port, Username and Password, each with its own copy button. Use it when you want to read or copy a single value.
List shows each endpoint as a single string in your chosen Proxy format, which is what you want for pasting several at once. There is a copy-all action for the whole set.
Per-row actions
| Action | What it does |
|---|---|
| Check proxy | Tests that endpoint now: reachability, the exit IP, and the latency the proxy adds |
| Replace | Swaps that endpoint for a fresh exit IP, and checks it automatically |
| Copy | Copies that endpoint in your chosen format |
Check proxy reports three things. Whether the endpoint works, the Exit IP it is currently presenting, and the Latency the proxy adds on top of the direct connection. Latency is the number that matters when a target is timing you out.
Replace is how you recover a single burned address without regenerating the whole set. Everything else in your set keeps its address.
Selecting Replace while Proxy checking is set to Manual generates the new endpoint without checking it, leaving the check to you. See My Account for that setting.
Regenerating everything
Regenerate proxies discards the current set and produces a fresh one. Because this changes every address at once, it is the wrong tool for one bad endpoint; use Replace for that.
A note on sticky sessions
Each generated endpoint carries its own session identifier, so every endpoint holds a stable exit IP for the life of its session rather than sharing one address with the rest of the set. There is no toggle for this, because there is no alternative worth offering. See Sticky Sessions.