Browserbase is a cloud platform that provides headless browser infrastructure for AI agents and web automation. Its REST API lets you programmatically create and manage browser sessions, contexts, agents, functions, extensions, certificates, and downloads, and retrieve session logs, recordings, and replays. Nexla connects to the Browserbase v1 API so you can ingest this operational data or push actions back to Browserbase.
Power end-to-end data operations for your Browserbase API with Nexla. Our bi-directional Browserbase connector is purpose-built for Browserbase, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Browserbase or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Browserbase workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Before creating a Browserbase credential, you need a Browserbase account and an API key. Browserbase authenticates every REST API request with an API key sent in the X-BB-API-Key header, so no OAuth flow or token exchange is required.
To obtain your Browserbase API key, follow these steps:
Locate your API Key in the settings dashboard. Your API key is displayed on the account overview so you can copy it directly.
Copy the API key and store it securely, as it grants programmatic access to your Browserbase projects and sessions and should be treated as sensitive information.
The API key authenticates your requests and scopes access to the projects associated with your account. If your API key is compromised, regenerate it from your Browserbase settings and update the credential in Nexla. For complete details about authentication and available endpoints, refer to the Browserbase API documentation.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Browserbase API key in the API Key field. This key is sent in the X-BB-API-Key header for all requests to the Browserbase API and must be kept confidential.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Browserbase connector tile, then select the credential that will be used to connect to Browserbase, and click Next; or, create a new Browserbase credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Browserbase endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.
[Rest API] Agents List
Retrieve Browserbase agents list via the Browserbase v1 API.
This endpoint returns the agents in your account and automatically follows cursor-based pagination to fetch all available records.
[Rest API] Agent Runs List
Retrieve Browserbase agent runs list via the Browserbase v1 API.
This endpoint returns the agent runs in your account and automatically follows cursor-based pagination to fetch all available records.
[Rest API] Agent Runs Messages
Retrieve Browserbase agent runs messages via the Browserbase v1 API.
Enter the Runid of the agent run whose messages you want to ingest. This path parameter is required to identify the specific run.
This endpoint automatically follows token-based pagination to fetch all available messages for the run.
[Rest API] Certificates List
Retrieve Browserbase certificates list via the Browserbase v1 API.
This endpoint returns the certificates configured in your account.
[Rest API] Downloads List
Retrieve Browserbase downloads list via the Browserbase v1 API.
This endpoint returns the downloads in your account and automatically follows offset-based pagination to fetch all available records.
[Rest API] Fetch Create
Retrieve Browserbase fetch create via the Browserbase v1 API.
Enter the Request Body as raw JSON. This endpoint issues a POST request and returns the response for the supplied payload.
[Rest API] Functions List
Retrieve Browserbase functions list via the Browserbase v1 API.
This endpoint returns the functions in your account and automatically follows offset-based pagination to fetch all available records.
[Rest API] Functions Versions
Retrieve Browserbase functions versions via the Browserbase v1 API.
Enter the Id of the function whose versions you want to ingest. This path parameter is required.
This endpoint automatically follows offset-based pagination to fetch all available versions.
[Rest API] Function Builds List
Retrieve Browserbase function builds list via the Browserbase v1 API.
This endpoint returns the function builds in your account and automatically follows offset-based pagination to fetch all available records.
[Rest API] Function Builds Logs
Retrieve Browserbase function builds logs via the Browserbase v1 API.
Enter the Id of the function build whose logs you want to ingest. This path parameter is required.
[Rest API] Function Invocations Logs
Retrieve Browserbase function invocations logs via the Browserbase v1 API.
Enter the Id of the function invocation whose logs you want to ingest. This path parameter is required.
[Rest API] Function Versions Invocations
Retrieve Browserbase function versions invocations via the Browserbase v1 API.
Enter the Id of the function version whose invocations you want to ingest. This path parameter is required.
This endpoint automatically follows offset-based pagination to fetch all available invocations.
[Rest API] Projects List
Retrieve Browserbase projects list via the Browserbase v1 API.
This endpoint returns the projects associated with your account.
[Rest API] Projects Usage
Retrieve Browserbase projects usage via the Browserbase v1 API.
Enter the Id of the project whose usage metrics you want to ingest. This path parameter is required.
[Rest API] Search Create
Retrieve Browserbase search create via the Browserbase v1 API.
Enter the Request Body as raw JSON. This endpoint issues a POST request and returns the search response for the supplied payload.
[Rest API] Sessions List
Retrieve Browserbase sessions list via the Browserbase v1 API.
This endpoint returns the browser sessions in your account.
[Rest API] Sessions Debug
Retrieve Browserbase sessions debug via the Browserbase v1 API.
Enter the Id of the session whose debug information you want to ingest. This path parameter is required.
[Rest API] Sessions Logs
Retrieve Browserbase sessions logs via the Browserbase v1 API.
Enter the Id of the session whose logs you want to ingest. This path parameter is required.
[Rest API] Sessions Recording
Retrieve Browserbase sessions recording via the Browserbase v1 API.
Enter the Id of the session whose recording you want to ingest. This path parameter is required.
[Rest API] Sessions Recording Downloads List
Retrieve Browserbase sessions recording downloads list via the Browserbase v1 API.
Enter the Id of the session whose recording downloads you want to ingest. This path parameter is required.
[Rest API] Sessions Replays List
Retrieve Browserbase sessions replays list via the Browserbase v1 API.
Enter the Id of the session whose replays you want to ingest. This path parameter is required.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Browserbase data sources can also be manually configured to ingest data from any valid Browserbase API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Browserbase data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Browserbase destination, and select the Send to Destination option from the menu. Select the Browserbase connector from the list of available destination connectors, then select the credential that will be used to connect to Browserbase, and click Next; or, create a new Browserbase credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Browserbase endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
[Rest API] Agents Create
Manage Browserbase agents create via the Browserbase v1 API.
Each record from your Nexset is sent as a JSON request body to create a new agent in Browserbase.
[Rest API] Agents Update
Manage Browserbase agents update via the Browserbase v1 API.
Enter the Agentid of the agent to update. This path parameter is required.
Each record from your Nexset is sent as a JSON request body to update the specified agent.
[Rest API] Agents Delete
Manage Browserbase agents delete via the Browserbase v1 API.
Enter the Agentid of the agent to delete. This path parameter is required.
[Rest API] Agent Runs Create
Manage Browserbase agent runs create via the Browserbase v1 API.
Each record from your Nexset is sent as a JSON request body to create a new agent run in Browserbase.
[Rest API] Agent Runs Stop
Manage Browserbase agent runs stop via the Browserbase v1 API.
Enter the Runid of the agent run to stop. This path parameter is required.
[Rest API] Certificates Delete
Manage Browserbase certificates delete via the Browserbase v1 API.
Enter the Id of the certificate to delete. This path parameter is required.
[Rest API] Contexts Create
Manage Browserbase contexts create via the Browserbase v1 API.
Each record from your Nexset is sent as a JSON request body to create a new context in Browserbase.
[Rest API] Contexts Update
Manage Browserbase contexts update via the Browserbase v1 API.
Enter the Id of the context to update. This path parameter is required.
[Rest API] Contexts Delete
Manage Browserbase contexts delete via the Browserbase v1 API.
Enter the Id of the context to delete. This path parameter is required.
[Rest API] Downloads Delete
Manage Browserbase downloads delete via the Browserbase v1 API.
Enter the Id of the download to delete. This path parameter is required.
[Rest API] Extensions Delete
Manage Browserbase extensions delete via the Browserbase v1 API.
Enter the Id of the extension to delete. This path parameter is required.
[Rest API] Functions Invoke
Manage Browserbase functions invoke via the Browserbase v1 API.
Enter the Id of the function to invoke. This path parameter is required.
Each record from your Nexset is sent as a JSON request body to invoke the specified function.
[Rest API] Sessions Create
Manage Browserbase sessions create via the Browserbase v1 API.
Each record from your Nexset is sent as a JSON request body to create a new browser session in Browserbase.
[Rest API] Sessions Update
Manage Browserbase sessions update via the Browserbase v1 API.
Enter the Id of the session to update. This path parameter is required.
Each record from your Nexset is sent as a JSON request body to update the specified session.
[Rest API] Sessions Recording Downloads Create
Manage Browserbase sessions recording downloads create via the Browserbase v1 API.
Enter the Id of the session whose recording download you want to create. This path parameter is required.
Browserbase destinations can also be manually configured to send data to any valid Browserbase API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Browserbase endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the Browserbase endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
