Overview of the Bytebot API endpoints
Bytebot’s core functionality is exposed through its Computer Use API, which provides a unified endpoint for all interactions with the desktop environment. The API allows for programmatic control of mouse movement, keyboard input, and screen capture.
The Bytebot API does not require authentication by default when accessed locally. For remote access, standard network security practices should be implemented.
All API endpoints are relative to the base URL:
The port can be configured when running the container.
Single endpoint for all desktop interactions including mouse, keyboard, and screen operations
Code examples and snippets for common automation scenarios
All API responses follow a standard JSON format:
When an error occurs, the API returns:
Common HTTP status codes:
Status Code | Description |
---|---|
200 | Success |
400 | Bad Request - Invalid parameters |
500 | Internal Server Error |
The API currently does not implement rate limiting, but excessive requests may impact performance of the virtual desktop environment.
Overview of the Bytebot API endpoints
Bytebot’s core functionality is exposed through its Computer Use API, which provides a unified endpoint for all interactions with the desktop environment. The API allows for programmatic control of mouse movement, keyboard input, and screen capture.
The Bytebot API does not require authentication by default when accessed locally. For remote access, standard network security practices should be implemented.
All API endpoints are relative to the base URL:
The port can be configured when running the container.
Single endpoint for all desktop interactions including mouse, keyboard, and screen operations
Code examples and snippets for common automation scenarios
All API responses follow a standard JSON format:
When an error occurs, the API returns:
Common HTTP status codes:
Status Code | Description |
---|---|
200 | Success |
400 | Bad Request - Invalid parameters |
500 | Internal Server Error |
The API currently does not implement rate limiting, but excessive requests may impact performance of the virtual desktop environment.