Keys / Browserbase

BROWSERBASE_API_KEY

The Browserbase API key your app starts cloud browser sessions with. Each project has one key, and the key picks the project.

Expires
the docs don't say
API
none; dashboard only

Get it

Create one on www.browserbase.com/settings. The steps aren't recorded yet.

Set it

BROWSERBASE_API_KEY=...

The Node.js and Python SDKs read it from this variable when you don't pass a key. Or keep it out of .env with keypin: keypin run -- npm run dev

Replace it

  1. A project has one key, and an Admin regenerates it in the dashboard. Regenerating revokes the old key at once.
  2. Requests with the old key get 401 until you deploy the new one, so deploy it right away everywhere that reads BROWSERBASE_API_KEY: .env files, CI variables, and Secrets used by deployed Functions.

Set rotate_every on the key in keypin.toml and a rotated date on its vault item, and keypin status shows when it's due.

Sources, checked 2026-11-16