Access to the Browser.lol API requires a specific subscription plan and is not included in the standard or premium tiers. If you are interested in leveraging our API for programmatic workspace management, please contact our support team to discuss custom plans and access.
Generating an API Key
To generate an API key, follow these steps:
1Log in to your Browser.lol account.
2Navigate to your Dashboard.
3Click on "API Keys" in the left-hand sidebar menu.
4In the "Create New API Key" modal window:
Optionally, enter a descriptive name for your key (e.g., "My Integration").
Optionally, set an expiration date. If left blank, the key will not expire.
5Click "Generate API Key".
6Your new API key will be displayed only once. Make sure to copy and store it securely. You will not be able to retrieve it again.
All API requests must include the API key in the Authorization header as a Bearer token:
Authorization Header
Authorization: Bearer YOUR_API_KEY
Security Notice
To protect your credentials, all API requests using your API key (i.e., those requiring the Authorization: Bearer header) should be made from your server-side environment. Do not expose your API key in client-side code (e.g., JavaScript running in a user's browser). The /vm endpoint described below is an exception, designed for client-side use with a temporary workspace ID.
API Base URL
All API endpoints can be accessed through the base domain: api.browser.lol
For example, to access the /v7/workspace/data endpoint, you would make a request to https://api.browser.lol/v7/workspace/data
Custom API Domain
Enterprise customers can request a custom API domain (e.g., api.your-company.com) for their API integration. To set up a custom API endpoint with your own domain, please contact our support team. Custom domains provide additional branding consistency and can help with network security policies in corporate environments.
API Endpoints
GET/v7/user/api
Get API Usage Statistics
Retrieves API usage statistics and limits for the authenticated user, including quota information and current usage in the billing cycle.
Initiates the creation of a new virtual browser workspace.
Required Headers
AuthorizationBearer tokenRequired
Content-Typeapplication/jsonRequired
Request Body (JSON)
{
"template_name": "Chrome", // Required: Name of the workspace template (e.g., "Chrome")
"layout": "us", // Optional: Keyboard layout (default "us")
"language": "en" // Optional: Browser language (default "en")
}
Body Field Descriptions
template_nameRequired
The name of the workspace template to use. Available templates are subject to your subscription plan.
layoutOptional
The keyboard layout for the virtual browser. Defaults to "us".
languageOptional
The browser language. Defaults to "en".
Success Response (200 OK)
Note: The workspace might not be immediately ready after this response. Use the /v7/workspace/data endpoint or poll the /vm endpoint to check the status.