GET /api/browser/:id/status

curl https://browser.rayobyte.com/api/browser/br_3f8a1c9d2e4b5a60/status \
  -H "x-api-key: rb_live_YOUR_KEY"

{
  "browserId": "br_3f8a1c9d2e4b5a60",
  "cdpUrl": "wss://sb-02.browser.rayobyte.com/cdp/br_5d4d8610784e2a91",
  "vncUrl": "https://sb-02.browser.rayobyte.com/vnc/vnc.html?path=ws%3Ftoken%3Dbr_5d4d8610784e2a91&autoconnect=true&resize=scale",
  "status": "ACTIVE",
  "createdAt": "2026-09-18T14:02:41.907Z",
  "expiresAt": "2026-09-18T16:02:41.907Z",
  "browserParams": {
    "os": "windows",
    "proxy": "http://USERNAME:***@us-east.gw.rayobyte.com:8000",
    "headless": false
  },
  "metadata": { "job": "crawl-42" }
}

The id in the path is the x-session-id value or the br_ id at the end of cdpUrl. Both return the same session.

Auth: x-api-key header.

Fields

Field	Notes
status	ACTIVE, CLOSED, DEAD or EXPIRED
expiresAt	When the lifetime runs out. This is the value to trust, because maxLifetime is clamped without telling you
cdpUrl	Rewritten into its public sb-NN.browser.rayobyte.com form
vncUrl	Present only when the browser was created with vnc=true

browserParams.proxy is the proxy you sent with the password masked as ***. metadata holds the object you passed on the create, and can carry keys the gateway adds alongside yours.

How long it stays readable

A session is readable for its maxLifetime plus one hour after it was created, then it is gone. A 404 on a session you know existed usually means it aged out, not that it never ran. The permanent record is GET /user/api/sessions.

Errors

Status	Message
401	Missing API key or Invalid API key
404	Session not found. Also the answer for a session that belongs to another account