Connection URLs and Endpoints
Browserless uses HTTPS for BrowserQL and REST APIs, and WebSocket connections for BaaS sessions. Pick the host that matches your fleet, then choose the path that matches your browser or API.
Shared Fleet vs. Private Fleet URLs
Browserless operates two types of fleets. Use the URLs that match your account type.
Shared fleet
The shared fleet uses regional URLs shared across all customers on that plan.
| Region | URL |
|---|---|
| US West | https://production-sfo.browserless.io |
| Europe UK | https://production-lon.browserless.io |
| Europe Amsterdam | https://production-ams.browserless.io |
For WebSocket connections, replace https:// with wss://.
Private fleet (Enterprise private deployments)
Enterprise customers with a dedicated fleet connect through chrome.browserless.io, which routes to your assigned region. Regional variants are available for lower latency.
| Region | URL |
|---|---|
| Default (auto-routed) | https://chrome.browserless.io |
| US West (SFO) | https://chrome-us-west.browserless.io |
| US East (NYC) | https://chrome-us-east.browserless.io |
| Europe UK (LON) | https://chrome-eu-uk.browserless.io |
| Europe Amsterdam (AMS) | https://chrome-eu-ams.browserless.io |
For WebSocket connections, replace https:// with wss://.
Using a private fleet token against a shared fleet URL returns HTTP 401 Unauthorized. Always use your dedicated fleet URL with your private fleet token.
See Load Balancing for more on private fleet regional endpoints.
BrowserQL Endpoints
BrowserQL uses HTTPS POST requests. Choose the endpoint that matches the browser you want.
| Purpose | Shared fleet URL | Notes |
|---|---|---|
| Chromium | https://production-sfo.browserless.io/chromium/bql?token=YOUR_TOKEN | Standard BrowserQL queries |
| Chrome | https://production-sfo.browserless.io/chrome/bql?token=YOUR_TOKEN | Chrome-based BrowserQL sessions |
| Stealth | https://production-sfo.browserless.io/stealth/bql?token=YOUR_TOKEN | Stealth-enabled BrowserQL sessions |
The same path patterns apply on dedicated fleets. Replace the shared-fleet host with chrome.browserless.io or your regional dedicated URL.
If you use the BQL IDE, Browserless handles the endpoint for you. If you reconnect to an existing BQL session, use the browserQLEndpoint returned by the reconnect mutation rather than building the reconnect URL by hand.
BaaS v2 Endpoints
To connect Puppeteer or Playwright to Browserless, use a WebSocket URL. These endpoints launch a browser and hand control back to your library.
| Library | Example URL |
|---|---|
| Puppeteer / Chromium | wss://production-sfo.browserless.io?token=YOUR_TOKEN |
| Playwright Chromium over CDP | wss://production-sfo.browserless.io?token=YOUR_TOKEN |
| Playwright native Chromium | wss://production-sfo.browserless.io/chromium/playwright?token=YOUR_TOKEN |
| Playwright Chrome | wss://production-sfo.browserless.io/chrome?token=YOUR_TOKEN |
| Playwright Firefox | wss://production-sfo.browserless.io/firefox/playwright?token=YOUR_TOKEN |
| Playwright WebKit | wss://production-sfo.browserless.io/webkit/playwright?token=YOUR_TOKEN |
Use the nearest region to reduce latency. See Load Balancers. All endpoints require the ?token= query parameter.
REST API Endpoints
Browserless provides REST API endpoints for common operations.
https://production-sfo.browserless.io/screenshot?token=YOUR_TOKEN
https://production-sfo.browserless.io/pdf?token=YOUR_TOKEN
https://production-sfo.browserless.io/content?token=YOUR_TOKEN
Using Your API Token
Add your API token to the URL query string as ?token=YOUR_TOKEN. Invalid tokens result in HTTP 401 or 403 responses. Keep the URL secure and avoid exposing it in client-side code or logs.
Launch Parameters and Options
See Launch Parameters for query parameters, the encoded JSON launch payload, and common options.