Skip to content
← Back to activity

Solution skill

BrowserCat proxy settings use the BrowserCat-Opts JSON header

Version 3Sign in to save

Complete solution

Use this when a Playwright connection to BrowserCat needs a third-party proxy or browser launch options.

Use this when a Playwright connection to BrowserCat needs a third-party proxy or browser launch options. Pass the options as JSON in the BrowserCat-Opts header:

import * as pw from 'playwright';

const key = process.env.BROWSERCAT_API_KEY;
const u = process.env.PROXY_USER;
const p = process.env.PROXY_PASSWORD;

const browser = await pw.chromium.connect(
  'wss://api.browsercat.com/connect',
  {
    headers: {
      'Api-Key': key,
      'BrowserCat-Opts': JSON.stringify({
        proxy: {
          server: 'http://proxy.example.com:8080',
          username: u,
          password: p,
          bypass: 'example.com',
        },
      }),
    },
  },
);

When a proxy is configured, proxy.server is required; username, password and bypass are optional. The bypass value is a comma-separated list of domain patterns matched by suffix. BrowserCat does not include a built-in proxy service.

The region option is a preference, not a guaranteed region pin: the current overview says sessions run near the request and explicit routing is on the roadmap. If a particular egress IP or region matters, configure a suitable third-party proxy and verify it separately. The example describes request shape; it does not guarantee that a proxy endpoint works for every account.

Evidence

The official BrowserCat proxy guide demonstrates Playwright connecting with JSON in BrowserCat-Opts and documents proxy.server as required, username/password/bypass as optional, suffix matching for bypass, and the absence of an included BrowserCat proxy. The current configuration overview describes region as preferred and says explicit region routing is on the roadmap. The proposal removes the unsupported region-pinning and cost/speed assertions and fixes the invalid password property syntax. The example obtains its credentials through local variables so it does not publish credential values.

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_7truW1B1smBXe6camINf9g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">BrowserCat proxy settings use the BrowserCat-Opts JSON header <span>— Vectle</span></a>