Per-Number Proxy (IP Isolation)

Per-Number Proxy routes each Unofficial-API number's traffic out through its own dedicated proxy IP. Instead of every number on the server sharing one IP address, each number can egress from a different IP — which reduces the IP-correlation that contributes to bulk bans. This is a v1.2 feature.

What it is

When you run several WhatsApp numbers from a single server, they would normally all connect from that server's one IP address. To WhatsApp, that looks like many accounts operating from the same place — a pattern that can get the whole group flagged together.

Per-Number Proxy breaks that link. You assign a separate proxy to each number, so each one reaches WhatsApp through its own IP. If one number runs into trouble, it is not automatically tied to all the others by a shared address.

Why and when to use it

  • Running many numbers from one server. This is the main use case — give each number its own IP so they are not all correlated by a single shared address.
  • Reducing bulk-ban risk. IP-correlation between accounts is one of the signals that contributes to bulk bans; isolating each number's traffic lowers that risk.
  • Keeping numbers independent. Problems on one number are less likely to spill over onto your other numbers when they do not share an outbound IP.

How it works

You assign a proxy to a number from the Devices screen. From then on, the heavy lifting happens automatically when that number's session starts:

  • The Node bridge fetches the number's assigned proxy as the session starts up.
  • It then runs a fail-closed preflight check: before connecting, it verifies the actual outbound IP (via an ipify lookup) to confirm the traffic really is leaving through the proxy.
  • If the proxy is wrong or down, the number will not connect — it refuses to fall back to the server's shared IP rather than silently leaking onto it.

Because each number connects through its own verified proxy, every number can egress from a different IP.

Why "fail-closed" matters: A fail-closed design means that when something goes wrong, the safe thing happens by default. Here, a broken proxy stops the connection instead of quietly routing that number through the shared server IP — which is exactly the leak you set up isolation to prevent.

How to set it up

  1. Make sure the feature is enabled for your workspace (it is gated by a feature flag and is off by default).
  2. Open the Devices screen (URL /devices).
  3. Find the number you want to isolate and open its proxy panel.
  4. Enter the proxy details for that number and save.
  5. Restart / reconnect that number's session. On start-up the Node bridge fetches the proxy and runs the fail-closed IP preflight; if the proxy is bad, the number stays disconnected rather than connecting on the wrong IP.
  6. Repeat for each number, assigning a different proxy to each one.
Caution: If a number's proxy is misconfigured or offline, that number will not connect at all — this is intentional, to stop it leaking onto the shared server IP. Make sure each assigned proxy is reachable, or remove the proxy assignment to let the number connect normally.

Where to find it

Proxy assignment lives on the Devices screen (URL /devices), where each number has its own proxy panel.

Plan availability

Per-Number Proxy is gated by a feature flag and is off by default. It applies to the Unofficial API engine. If you do not see the proxy panel on the Devices screen, the feature is not enabled for your workspace — contact the platform owner to turn it on.

  • Connect a Channel — how to add the Unofficial-API numbers you then isolate.
  • Multi-Engine — running the Unofficial API alongside the official channels.
  • WhatsApp Warmer — another per-number safeguard that pairs well with IP isolation to reduce ban risk.
WaDesk Documentation