How it works

Service Description

Our on-demand cloud browsers service allows users to create web browser instances via an HTTP API call authenticated with a token. This service is designed to provide a secure and customizable web browsing experience, ideal for automated testing, web scraping, or any other need requiring a dynamic web browser.

How It Works

1. Browser Creation Request:

Users send an HTTP request to our service’s API to create a browser. This request must include a valid authentication token in the header.

2. Authentication:

The service verifies the provided token. If the token is not valid, the request is rejected with an HTTP 401 (Unauthorized) status code.

3. Browser Launch:

Once the request is authenticated, the service configures and launches a new instance of a web browser. This browser is started with specific options to ensure it operates optimally and securely in a containerized environment.

4. WebSocket Endpoint Provisioning:

After launching the browser, the service returns a WebSocket URL. This URL allows users to connect directly to the newly created browser and interact with it in real-time.

5. Browser Management:

The service also monitors the browser’s status to ensure it is operating correctly. If there are any issues during the browser’s launch or operation, they are handled and logged appropriately for resolution.

6. Containerized Environment Execution:

The service is designed to operate in a containerized environment, ensuring scalability and reliability. Each browser runs in its own container, isolated from others.

Example Workflow

1. Make a Request:

The user sends an HTTP request to the /api/v1/Browser/Open or /api/v1/Browser/OpenAdvanced endpoint with an authentication token in the header.

2. Reception and Authentication:

The service receives the request and verifies the token. If the token is valid, it proceeds to the next step.

3. Browser Launch:

The service configures and launches a web browser according to the predefined parameters.

4. Response with WebSocket URL:

The service responds with a WebSocket URL that the user can use to connect to the browser.

5. Interaction with the Browser:

The user connects to the browser via the WebSocket URL and can interact with it in real-time.

Security Considerations

• Token Authentication: Only requests with valid tokens are processed, ensuring that only authorized users can create and access browsers.

• Container Isolation: Each browser runs in its own container, providing a secure and isolated environment.

Scalability and Reliability

The container-based design allows for horizontal scaling, adding more instances as demand increases, and ensures that each browser operates in a controlled and consistent environment.

Contact and Support

For more information, technical support, or inquiries about the service, please contact our support team.