Egress & Proxies

Every browser session routes its network traffic through an egress profile that determines the outbound IP address. You can choose between shared IPs, dedicated IPs, residential IPs, or your own proxy.

Available Egress Profiles

Setting the Egress Profile

Pass egressProfile when creating a session:

curl -X POST "https://api.boxes.banata.dev/v1/browsers" \
  -H "Authorization: Bearer br_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "weight": "medium",
    "isolation": "dedicated",
    "egressProfile": "dedicated-dc",
    "stealth": true
  }'

Default behavior

If you do not specify egressProfile, it is determined automatically:

• If you provide a proxy object → defaults to byo-proxy
• If isolation is dedicated → defaults to dedicated-dc
• Otherwise → defaults to shared-dc

Rules

1. Non-shared egress requires dedicated isolation. If you set egressProfile to anything other than shared-dc, you must also set isolation to "dedicated". Otherwise the API returns a 400 error.

2. BYO proxy requires a proxy config. If egressProfile is "byo-proxy", you must include a proxy object with at least protocol, host, and port.

3. Proxy config requires BYO proxy. If you include a proxy object, egressProfile must be "byo-proxy" (or it will default to "byo-proxy" automatically).

Bring Your Own Proxy

Route all browser traffic through your own proxy server:

{
  "weight": "light",
  "egressProfile": "byo-proxy",
  "proxy": {
    "protocol": "http",
    "host": "proxy.example.com",
    "port": 8080,
    "username": "user",
    "password": "pass"
  }
}

All browser network requests (including WebSocket connections, XHR, and resource loads) route through the proxy.

Note: You do not need dedicated isolation to use BYO proxy. You can use byo-proxy with shared isolation on any plan.

Choosing the Right Profile

Shared datacenter (shared-dc)

Best for general-purpose automation where IP identity is not critical. This is the default and most cost-efficient option.

• Simple scraping of sites without IP-based blocking
• Testing and QA against your own applications
• General browser automation

Dedicated datacenter (dedicated-dc)

Best when you need a consistent IP address for the session duration and do not want other sessions sharing your IP.

• Sites that track and rate-limit by IP
• Workflows that require a stable IP identity
• Compliance requirements for IP isolation

Rotating residential (rotating-residential)

Best for accessing sites that block datacenter IPs. The IP rotates from a pool of residential addresses.

• Scraping sites that aggressively block datacenter IP ranges
• Accessing geo-restricted content from residential IPs
• High-volume automation where IP rotation prevents rate limiting

Static residential (static-residential)

Best when you need a residential IP that stays the same for the entire session.

• Login flows on sites that flag IP changes
• Multi-step workflows where IP consistency is required
• Combining residential identity with session persistence

Bring your own proxy (byo-proxy)

Best when you have existing proxy infrastructure or need specific proxy providers.

• Using your existing residential or datacenter proxy subscriptions
• Proxy providers with custom features (geo-targeting, session control)
• Corporate network routing requirements

Combining Egress with Stealth

For the strongest anti-detection posture, combine stealth mode with residential egress:

{
  "weight": "medium",
  "isolation": "dedicated",
  "egressProfile": "rotating-residential",
  "stealth": true
}

This gives you:

• Realistic browser fingerprint (stealth)
• Residential IP address (egress)
• Dedicated machine resources (isolation)

Error Responses

Next Steps

• Browser Sessions — All session creation options
• Stealth & Anti-Detection — Browser fingerprint spoofing
• Billing & Plans — Feature availability per plan