Watch your browsers live

Via dashboard

From the dashboard you can list the browsers you have launched, to identify them easily you can make use of tags when creating them.

Once you identify your browser you can start a remote desktop directly from the dashboard using a screen icon.

The remote desktop startup process may take a few seconds. And in case you have not specified a label for the browser, the field will be empty.

Via HTTP API

1. /StartRemoteDesktop – Start Remote Desktop

Method: POST

Description: This endpoint starts a remote desktop session for the browser. The request must include the address of the browser session that was provided when the browser was created.

Request Body:

curl -X POST https://production.cloudbrowser.ai/api/v1/Browser/StartRemoteDesktop \
-H "Authorization: Bearer <your-api-token>" \
-d '{
    "address": "browserprovider-worker-*.cloudbrowser.ai"
}'

Response:

{
    "password": "remote_desktop_password",
    "success": true,
    "status": 200
}

• password: The password needed to access the remote desktop.

• success: true if the operation was successful, false otherwise.

• status: 200 for success, or another number for an error.

2. /StopRemoteDesktop – Stop Remote Desktop

Method: POST

Description: This endpoint stops an active remote desktop session. The request must include the address of the browser session that was provided when the browser was created.

Request Body:

curl -X POST https://production.cloudbrowser.ai/api/v1/Browser/StopRemoteDesktop \
-H "Authorization: Bearer <your-api-token>" \
-d '{
    "address": "browserprovider-worker-*.cloudbrowser.ai"
}'

Response:

{
    "success": true,
    "status": 200
}

• success: true if the operation was successful, false otherwise.

• status: 200 for success, or another number for an error.

Other considerations

The appearance and functionality of the remote desktop is limited for security reasons, however this does not represent any limitation on how the browser behaves in the production environment.

Likewise, the possible latency experienced on the remote desktop does not represent the actual browser performance.