Skip to main content
Quick Connect is the dashboard’s connection-string builder. You pick what you want — country, session type, rotation, error handling — and the dashboard generates the connection string you paste into your code or HTTP client. It’s also the name of the underlying mode. Putting rules directly into the connection string (country-us-session-job1-rotate-timed_300:pk_abc123@proxy.soax.com:1337) is “Quick Connect” no matter where you typed the string. The dashboard tool just makes building one easier.

​
When to use Quick Connect

Quick Connect covers everything most integrations need:
  • Rotating proxies (no session) and ephemeral sessions
  • Full filtering (country, region, city, ISP, ASN, zip, network)
  • Rotation (rotate-timed_N, rotate-requests_N)
  • Error handling (onerror-replace, onerror-retry_N, onerror-fail)
  • Routing preferences (prefer-lookalike)
  • Node binding (bind-node)
  • Unlimited concurrent sessions

​
Opening Quick Connect

In the dashboard, click Packages in the sidebar and open the package you want to use. The Quick Connect panel is on the package page.

​
Building a connection string

Quick Connect walks you through four groups of options, which match the four categories of rules under the hood:

​
1. Filtering — which nodes are eligible

The more specific your filter combination, the smaller the eligible pool. If you target a small city and a specific ISP, you may see slower allocation or NODE_NOT_FOUND errors. Start broad and narrow only when you need to.

​
2. Session — rotating or held

Session IDs are letters, digits, and underscores, up to 32 characters. Ephemeral sessions expire after 60 seconds of inactivity. Rules are locked on the first request — sending the same session ID with different rules returns 409 SESSION_PARAMS_MISMATCH. To change rules, use a new session ID.

​
3. Rotation — when the node is allowed to change

Only meaningful with a session.

​
4. Error handling — what happens on node failure

SOAX can only see infrastructure failures (node offline, connection refused, timeout). HTTP status codes from the target — 403, 429, CAPTCHA pages — are inside the HTTPS tunnel and aren’t visible to SOAX. Detecting and responding to those is your application’s job. See CAPTCHA & ban rates.

​
Routing and binding (optional)

bind-node requires a session and is incompatible with rotate-timed_N, rotate-requests_N, onerror-replace, and prefer-lookalike.

​
Copy and test

When your settings produce the connection string you want, click Copy to grab it. The format is:
Test it with one request:
A successful response includes a JSON body with the exit IP and its geolocation. If you targeted a country, the country_code should match.

​
Worked examples

Rotating US residential, no session:
Session in the UK, rotate IP every 5 minutes:
Mobile in New York, retry 3 times on error, prefer a similar replacement:
Lock to a single node:

​
Next steps

Authentication

Username/password and IP Auth, end-to-end.

Residential proxies

Full rule reference for residential configuration.

Mobile proxies

Full rule reference for mobile configuration.

Error codes

What each SOAX-level error means and how to fix it.