Browser automation infrastructure made simple on BrowserBee

Quickstart

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

Before you begin
#

Make sure you have:

your BrowserBee account email and password
network access to the BrowserBee API
a terminal with curl available

BrowserBee currently publishes these API base URLs:

Authentication

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

Authentication modes
#

BrowserBee currently uses two authentication patterns:

Use case	Authentication mode	Endpoint examples
Create an API token	HTTP Basic	`POST /tokens`
Normal API operations	Bearer token	`/browsers`, `/tokens/{id}`, `/webhooks`

Creating tokens with Basic auth
#

Use your BrowserBee account email and password when creating a new token:

Browser profiles

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

What a browser profile represents
#

A BrowserBee profile is a named, versioned browser runtime definition. It combines the browser identity with the operational defaults your teams expect when they automate against it.

Webhooks

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

Why use webhooks
#

Webhooks allow BrowserBee to notify your systems when profile state changes, which reduces polling and helps your automation react faster.

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.

API overview

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

Base URLs
#

Environment	Base URL
Production	`https://api.browserbee.com/api/v1`
Development	`https://api-dev.browserbee.com/api/v1`

Resource groups
#

Health
#

Method	Path	Purpose
`GET`	`/up`	Liveness probe
`GET`	`/ready`	Readiness probe

Browser profiles
#

Method	Path	Purpose
`GET`	`/browsers`	List browser profiles
`POST`	`/browsers`	Create browser profile
`GET`	`/browsers/{profile_key}`	Get browser profile
`PATCH`	`/browsers/{profile_key}`	Update browser profile
`PUT`	`/browsers/{profile_key}`	Replace browser profile
`DELETE`	`/browsers/{profile_key}`	Delete browser profile
`POST`	`/browsers/{profile_key}/activate`	Mark profile as available
`POST`	`/browsers/{profile_key}/deprecate`	Mark profile as deprecated

Tokens
#

Method	Path	Purpose
`GET`	`/tokens`	List active API tokens
`POST`	`/tokens`	Create API token with Basic auth
`DELETE`	`/tokens/{id}`	Revoke API token

Webhooks
#

Method	Path	Purpose
`GET`	`/webhooks`	List registered webhooks
`POST`	`/webhooks`	Register a webhook
`DELETE`	`/webhooks/{id}`	Deactivate a webhook

Common response patterns
#

Status	Meaning
`200`	Successful read or state transition
`201`	Resource created
`204`	Resource removed or revoked without a body
`401`	Missing or invalid credentials
`404`	Resource was not found
`422`	Validation failed

Schemas worth knowing
#

The most important BrowserBee response objects for customer integrations are:

Common issues

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

`401 unauthorized`
#

This usually means one of three things:

you used a Bearer token where Basic auth was required for POST /tokens
the Bearer token is missing, expired in storage, or copied incorrectly
your automation is pointed at the wrong BrowserBee environment

`404` when reading a browser profile
#

The profile key in the URL does not match an existing BrowserBee profile.

Welcome to your Hugo template

Thu, 16 Apr 2026 00:00:00 +0000

You now have a ready-to-clone Hugo static site repository template.

Edit this post or delete it and create your own content with:

hugo new content posts/my-first-post.md

About

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

This is a starter page for your project.

Replace this content with details about your site, team, or product.

API and Webhooks

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

BrowserBee exposes a practical API surface and webhook events so teams can move browser automation into repeatable delivery workflows.

What teams build with it
#

CI pipeline steps that create and manage profiles
Internal tooling that orchestrates browser automation operations
Notification and incident hooks for critical lifecycle events

Integration patterns
#

Pipeline-driven profile management
Event forwarding into chat, ticketing, and incident tools
Environment gate checks before release promotion

Value for teams
#

Less manual coordination between QA and platform engineers
Better traceability for browser automation operations
Faster feedback in release workflows

Start with docs and implementation guides.

Browser Profile Manager

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

The Browser Profile Manager helps teams define, version, and reuse browser profiles without one-off configuration drift.

Key capabilities
#

Reusable profile definitions across projects
Controlled updates for profile configuration changes
Environment-specific profile standards
Cleaner ownership between development, QA, and platform teams

Why it matters
#

Unmanaged browser setup causes inconsistent test behavior. Standardized profiles reduce variability and make failures easier to diagnose.

Contact

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

E-commerce Reliability

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

E-commerce teams rely on browser-based journeys where small failures can affect conversion. BrowserBee helps protect those critical paths with repeatable automation.

High-impact flows
#

Product browsing and search
Cart and checkout workflows
Account and order management experiences

BrowserBee approach
#

Consistent profile inputs for journey validation
Pipeline integration for pre-release flow checks
Event-driven hooks for incident awareness and response

Why this matters
#

Better confidence in customer-facing changes
Faster isolation of regression causes
Reduced operational surprises during peak periods

Review onboarding docs and contact us for implementation support.

Enterprise Control Plane

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

Enterprise teams use BrowserBee as a control plane for policy, visibility, and standard workflow contracts across multiple engineering groups.

Control-plane priorities
#

Shared standards for browser automation inputs
Clear environment boundaries and operating responsibilities
Unified observability and readiness signals
Repeatable onboarding for new teams

Operating model
#

Platform team defines baseline conventions
Product teams adopt standardized integration patterns
QA teams align reliability checks with release criteria

Why this matters at scale
#

As adoption grows, unmanaged automation creates operational variance. A control-plane model reduces variance and improves release predictability.

Features

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

Feature set

Everything you need to run browser automation with confidence

Give engineering teams one reliable layer for browser coverage, execution health, and ongoing test stability.

Works with your existing CI/CD and test stack

Integration Guides

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

Integration guides focus on the workflows teams repeat every week, not one-time setup.

Priority integrations
#

CI pipeline integration for browser profile operations
Webhook event routing to internal systems
Health and readiness checks in deployment controls

Implementation checklist
#

Validate authentication and access boundaries.
Define profile naming and environment conventions.
Add automated checks in CI and release gates.
Document failure handling and recovery playbooks.

Related docs
#

Learning Paths

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

BrowserBee learning paths help different roles ramp with the right depth at the right time.

Developer path
#

Complete quickstart and authentication setup
Automate basic profile operations via API
Integrate first workflow into CI

QA path
#

Standardize profile conventions across suites
Add repeatable validation checkpoints
Use troubleshooting patterns during rollout

Platform path
#

Define governance and operating contracts
Establish readiness and monitoring expectations
Create team onboarding playbooks

Recommended starting point
#

Onboarding Playbooks

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

Use these onboarding playbook patterns to move from pilot to scaled adoption.

Playbook 1: Pilot with one product team
#

Select one critical browser workflow
Implement profile standards and API checks
Measure reliability and rollout speed improvements

Playbook 2: Expand to QA organization
#

Share profile conventions and ownership model
Align failure triage workflows
Add quality gates in release pipelines

Playbook 3: Platform-driven scale
#

Publish organization-wide integration standards
Create reusable CI templates
Enable team-by-team adoption with documented checkpoints

What success looks like
#

Teams launch faster with fewer setup questions
Automation failures are easier to diagnose
Release quality signals are consistently applied

Need a tailored rollout sequence? Contact BrowserBee.

Platform Overview

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

BrowserBee provides a managed browser automation layer for teams that need predictable execution, reusable profiles, and stable integration contracts.

What this product covers
#

Central browser profile lifecycle management
API-first workflow automation for CI/CD and internal tooling
Event-driven integration via webhooks
Operational visibility with health and readiness signals

Who this is for
#

Engineering teams standardizing test and automation workflows
QA teams reducing flaky environment drift
Platform teams enforcing repeatable integration patterns

Typical adoption flow
#

Set profile conventions by environment.
Integrate profile operations into CI jobs.
Connect webhook events to internal systems.
Monitor reliability signals before and after releases.

Outcomes
#

Faster onboarding for new teams
Lower test instability from inconsistent setup
Better release confidence with explicit operational checks

Explore pricing or contact BrowserBee for implementation planning.

Platform Standardization

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

Platform teams are often responsible for making automation consistent across many engineering groups. BrowserBee supports that standardization effort.

Standardization goals
#

Shared browser automation conventions
Policy-aligned integration patterns
Operational visibility across teams and environments

Practical operating model
#

Define browser profile standards.
Publish API and webhook integration contracts.
Align readiness checks with release controls.
Scale adoption through documented playbooks.

Results
#

Lower cross-team variance
Faster onboarding for new products
Better governance without slowing delivery

See resources for onboarding playbooks and learning paths.

Pricing

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

Pricing that scales with your team

Choose the plan that fits today and scale when you are ready.

For individuals

Starter

For individuals and small teams.

$19.99/month

1 workspace
Up to 3 team members
Core automations
Community support

Get started

Coming soon

Products

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

Products

Browser automation products designed for modern delivery teams

A practical product suite for standardizing browser workflows, scaling automation, and improving release confidence.

Works with your existing CI/CD and test stack

Quality Assurance

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

Quality Assurance teams use BrowserBee to reduce test instability and improve confidence in release readiness.

QA challenges BrowserBee addresses
#

Inconsistent browser setup across environments
Time lost triaging non-deterministic failures
Weak visibility into automation readiness before release windows

How BrowserBee helps QA teams
#

Standardized browser profile management
API-driven workflow repeatability
Readiness signals that can be used in release criteria

Outcomes for QA organizations
#

Lower flake rates from environment drift
Faster incident triage and ownership clarity
More reliable pre-release validation cycles

Explore docs for QA-aligned implementation guidance.

Resources

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

Resources

Learning and launch resources for BrowserBee adoption

Use role-based materials to move from initial setup to reliable production workflows.

View docs Contact us

Updated regularly by the BrowserBee team

SaaS Release Confidence

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

SaaS teams need rapid iteration and high confidence. BrowserBee supports release workflows where browser automation is a quality gate, not a bottleneck.

Target use case
#

Frequent releases with strict reliability expectations
Multi-team ownership across feature development and QA
Continuous validation before promotion to production

BrowserBee contribution
#

Standardized profile execution across stages
Automated integration with deployment pipelines
Health and readiness checks that strengthen release gates

Business impact
#

Reduced release risk from late-stage browser issues
Faster recovery from automation regressions
More predictable delivery cadence

Solutions

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

Solutions

Solutions designed for teams, industries, and outcomes

BrowserBee helps teams solve browser automation reliability problems based on role, delivery model, and business risk.

Works with your existing CI/CD and test stack

Test Automation

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

Test automation programs often fail to scale because configuration and orchestration are inconsistent. BrowserBee gives teams a stable operating layer.

Common automation pain points
#

Ad hoc scripting around browser setup
Pipeline brittleness caused by hidden dependencies
Slow handoffs between developers, QA, and platform teams

BrowserBee solution
#

Reusable browser profiles across test suites
API contracts that fit directly into CI/CD workflows
Webhook events for downstream automation and reporting

Value at scale
#

Cleaner automation architecture
Faster execution onboarding for new projects
Better change control for test infrastructure

See CI integration guidance.

Browser automation infrastructure made simple on BrowserBee

Quickstart

Before you begin #

Authentication

Authentication modes #

Creating tokens with Basic auth #

Browser profiles

What a browser profile represents #

Webhooks

Why use webhooks #

Manage browser profiles

Typical profile workflow #

Create a profile #

Update or replace a profile #

Integrate with CI

Integration pattern #

Recommended default #

API overview

Base URLs #

Resource groups #

Health #

Browser profiles #

Tokens #

Webhooks #

Common response patterns #

Schemas worth knowing #

Common issues

401 unauthorized #

404 when reading a browser profile #

Welcome to your Hugo template

About

API and Webhooks

What teams build with it #

Integration patterns #

Value for teams #

Browser Profile Manager

Key capabilities #

Why it matters #

Contact

E-commerce Reliability

High-impact flows #

BrowserBee approach #

Why this matters #

Enterprise Control Plane

Control-plane priorities #

Operating model #

Why this matters at scale #

Features

Everything you need to run browser automation with confidence

Integration Guides

Priority integrations #

Implementation checklist #

Related docs #

Learning Paths

Developer path #

QA path #

Platform path #

Recommended starting point #

Onboarding Playbooks

Playbook 1: Pilot with one product team #

Playbook 2: Expand to QA organization #

Playbook 3: Platform-driven scale #

What success looks like #

Platform Overview

What this product covers #

Who this is for #

Typical adoption flow #

Outcomes #

Platform Standardization

Standardization goals #

Practical operating model #

Results #

Pricing

Pricing that scales with your team

Starter

Products

Browser automation products designed for modern delivery teams

Quality Assurance

QA challenges BrowserBee addresses #

How BrowserBee helps QA teams #

Before you begin
#

Authentication modes
#

Creating tokens with Basic auth
#

What a browser profile represents
#

Why use webhooks
#

Typical profile workflow
#

Create a profile
#

Update or replace a profile
#

Integration pattern
#

Recommended default
#

Base URLs
#

Resource groups
#

Health
#

Browser profiles
#

Tokens
#

Webhooks
#

Common response patterns
#

Schemas worth knowing
#

`401 unauthorized`
#

`404` when reading a browser profile
#

What teams build with it
#

Integration patterns
#

Value for teams
#

Key capabilities
#

Why it matters
#

High-impact flows
#

BrowserBee approach
#

Why this matters
#

Control-plane priorities
#

Operating model
#

Why this matters at scale
#

Priority integrations
#

Implementation checklist
#

Related docs
#

Developer path
#

QA path
#

Platform path
#

Recommended starting point
#

Playbook 1: Pilot with one product team
#

Playbook 2: Expand to QA organization
#

Playbook 3: Platform-driven scale
#

What success looks like
#

What this product covers
#

Who this is for
#

Typical adoption flow
#

Outcomes
#

Standardization goals
#

Practical operating model
#

Results
#

QA challenges BrowserBee addresses
#

How BrowserBee helps QA teams
#

Outcomes for QA organizations
#

Target use case
#

BrowserBee contribution
#

Business impact
#

Common automation pain points
#

BrowserBee solution
#

Value at scale
#