Manage browser profiles

Mon, 01 Jan 0001 00:00:00 +0000

Typical profile workflow
#

Most teams follow a simple lifecycle:

create a profile
validate it in limited automation
activate it for broader use
deprecate it before retirement
delete it when no longer needed

Create a profile
#

curl --request POST "https://api.browserbee.com/api/v1/browsers" \
 --header "Authorization: Bearer ${BROWSERBEE_API_TOKEN}" \
 --header "Content-Type: application/json" \
 --data '{
 "profile_key": "firefox-beta-linux",
 "name": "Firefox Beta on Linux",
 "channel": "beta",
 "version": "137",
 "status": "preview",
 "capabilities": ["webdriver", "video"],
 "platforms": ["linux"],
 "configuration": {
 "timeout_seconds": 120,
 "retry_attempts": 1,
 "headless": true
 }
 }'

Update or replace a profile
#

Use PATCH for incremental updates or PUT when your workflow treats the profile definition as the full source of truth.

Integrate with CI

Mon, 01 Jan 0001 00:00:00 +0000

Integration pattern
#

Most customers integrate BrowserBee at two points in CI:

a setup phase that verifies the required profile exists and is in the expected state
an operational phase that reacts to BrowserBee changes through webhooks or scheduled syncs

Recommended default
#

Store the BrowserBee token as a pipeline secret and validate access before your test jobs begin.

Guides on BrowserBee

Manage browser profiles

Typical profile workflow #

Create a profile #

Update or replace a profile #