Provides client-side access to the virtual machine interface for a specific workspace. This endpoint is intended to be used in the user's browser (e.g., by redirecting the user or embedding within an iframe) after obtaining a workspace ID from the /v7/workspace/create
endpoint.
Note that the base URL for this client-side endpoint differs from the server-side API base URL. If you are using the standard api.browser.lol
domain for server-side calls, use https://browser.lol/vm
for this endpoint. If you have a custom API domain (e.g., api.your-company.com
), use that same custom domain for this endpoint (e.g., https://api.your-company.com/vm
).
Note: This endpoint is designed for client-side access and does not use the Authorization: Bearer YOUR_API_KEY
header. Access is granted based on the validity of the workspace ID.
Query Parameters
id
(String): The unique identifier of the workspace (VM) to access. This is the workspaceName
returned by the /v7/workspace/create
endpoint. (Required)redirectUrl
(String): A URL to redirect the user to when they click the "Exit" or "Close" button within the VM interface. (Optional)logo
(String): A URL pointing to a publicly accessible JPG or PNG image. This logo will be displayed on the loading screen while the workspace is preparing. (Optional)
Example URLs:
- Standard Domain:
https://browser.lol/vm?id=...&redirectUrl=...&logo=...
- Custom Domain:
https://api.your-company.com/vm?id=...&redirectUrl=...&logo=...
Response (200 OK)
This endpoint always returns an HTTP status code of 200 OK
. The response body will be an HTML page containing either:
- The interactive interface for the requested virtual machine.
- An error message indicating why the workspace could not be accessed (e.g., invalid ID, expired session).
The response body is always HTML, not JSON.
Error Handling
If the workspace ID is invalid, expired, cannot be found, or if there is any other issue preventing access, the endpoint still returns a 200 OK
status code. The error condition will be described within the HTML content of the response page. There are no separate HTTP error status codes (like 404 or 403) used for this endpoint.
Check the content of the returned HTML page to determine if access was successful or if an error occurred.