Skip to main content

/json/version API

The /json/version API returns version information about the browser and DevTools protocol running on your Browserless instance. This is part of the standard Chrome DevTools Protocol and is available on both self-hosted and dedicated accounts.

Querying browser version

Issue a GET request to /json/version:

curl -X GET \
https://production-sfo.browserless.io/json/version?token=YOUR_API_TOKEN_HERE

Running this request will result in a JSON output like:

{
"Browser": "Chrome/145.0.7632.6",
"Protocol-Version": "1.3",
"User-Agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/145.0.0.0 Safari/537.36",
"V8-Version": "14.5.201.2",
"WebKit-Version": "537.36 (@47e20adcc15fc15f01825aa17e570c8f5492ac0f)",
"webSocketDebuggerUrl": "ws://chrome.browserless.io",
"Debugger-Version": "47e20adcc15fc15f01825aa17e570c8f5492ac0f"
}

Response fields

FieldTypeDescription
BrowserstringBrowser name and version
Protocol-VersionstringChrome DevTools Protocol version
User-AgentstringFull user-agent string of the bundled browser
V8-VersionstringV8 JavaScript engine version
WebKit-VersionstringWebKit rendering engine version and commit hash
webSocketDebuggerUrlstringBase WebSocket URL for CDP connections
Debugger-VersionstringDevTools debugger commit hash

Common use cases

  • Version matching: Verify the bundled Chromium version matches your client library (see Image Versions)
  • Debugging: Confirm the protocol version when troubleshooting CDP compatibility issues
  • Monitoring: Track browser versions across your fleet to ensure consistency after upgrades