Share the static residential exit shown in the console with a partner allowlist. A sticky session is not a static IP. Do not assume a partner will accept residential exits. Not for mainland China.
Some payment, ads, data, or API partners ask you to declare a stable exit before they add it to an allowlist. The product that fits a term-long, checkable address is static residential—not a rotating pool that may change per request.
Do not assume a partner will accept residential exits, or static residential exits in particular. Their policy is theirs. This page only explains what to copy from the console or order, and why a sticky session is not a leased fixed IP. For the definition, see what is a residential proxy. Not for mainland China. Use only lawful, authorized integrations.
First: do they need a fixed exit, or only a short-lived same IP?
| What you actually need | Typical fit | Do not treat as |
|---|---|---|
| The partner will write down one address and expect it to stay stable for your term | Static residential (billed per IP·month) | A rotating gateway hostname, or one sticky session |
| You only need the same exit for minutes, and nobody is maintaining a long-lived list | Sticky session on rotating residential (console fields only) | A static monthly lease |
| Batch sampling, changing exits are fine, no allowlist | Rotating residential (per GB) | Handing every new exit to the partner as a “fixed IP” |
Overview: rotating vs static. Shared versus dedicated static: shared vs dedicated. An allowlist cares about the address; whether the partner also cares that others may share it is their policy. This page does not invent isolation guarantees.
What to send the partner
An allowlist usually wants the exit IP their servers will see—not necessarily the proxy hostname you type in a client. After the static instance is provisioned, copy the exit from the console or order. Optionally confirm it with a curl check: send an authorized request that can show the source IP, and only then share the value if it matches the console.
| What to send | Where it comes from | Watch-outs |
|---|---|---|
| Exit IP | Console / static order instance; confirm with an authorized check if needed | Do not send a rotating gateway or any placeholder from this article |
| Protocol and port (only if they connect to your proxy entry, not merely allow your exit) | The same order return | Most allowlists permit the source IP they see; ask which one they need |
| Validity window | The order term in the console | After expiry, release, or replacement, the old address may no longer be yours—tell the partner to update |
Commands and fields: Docs EN quickstart. String shapes: proxy format.
Why a sticky session is not an allowlist address
Sticky is a short window on rotating residential. When the window ends, the node changes, or the session cannot be held, the exit can move. Firewall or risk lists that expect one address will then fail open or fail closed. If you need a relatively fixed identity for the term, order static—do not write a temporary sticky IP into a long-lived partner list.
Compliance and scope
Do not guess or spoof an exit type the partner has not approved. ZTProxy sells residential only—not datacenter, mobile, or marketing-ISP SKUs. Prices follow the console and pricing (rotating about $0.40/GB, about $0.20/GB on a 100 TB full bundle; static about $1.50 shared and about $5 dedicated per IP/month). USDT/USDC available; Visa/Mastercard in application. Not for mainland China.
FAQ
The partner asked for a “static ISP” or a cloud-provider IP. Can you guarantee approval?
No. Allowlist rules are set by the partner. We offer static residential exits, we do not sell ISP or datacenter SKUs, and we cannot promise that a given platform will accept a residential address.
Can I send the IP I saw during a sticky session?
Not as a long-lived list entry. Sticky can change when the window ends. Use static if you need a term-long address.
Can the rotating gateway hostname go on the allowlist?
Usually no. The gateway is where you connect; the partner sees the exit, which can change on rotating residential.
Does shared versus dedicated change the allowlist?
You still send that instance’s exit IP. Whether they accept an address that may be shared is their decision. See shared vs dedicated.
Will the address change mid-term?
Follow the console and the order. After renewal, release, or replacement, re-check and ask the partner to update the list. This page does not invent an availability SLA.
Should I also send the proxy username and password?
Allowlists usually need only the source IP they will see. Keep gateway credentials in your own client; do not spread them with the list.
Can I apply with the example address in this article?
No. Examples are not production exits. Use the current console value.
Where are prices confirmed?
In the console and on pricing.
Next steps
- Confirm the static instance is active in the console and copy the exit IP.
- Check it against an authorized target.
- Send the console address to the partner and ask whether they accept that exit type. When you are ready to order, open static residential or review rotating residential.