Create a pool
Create a browser pool with a specified size and configuration. All browsers in the pool share the same settings.Pool configuration options
Pools can be pre-configured with options like custom extensions, supported viewports, residential proxies, profiles, and more. See the API reference for more details.Acquire a browser
Acquire a browser from the pool. The request returns immediately if a browser is available, or waits until one becomes available. Theacquire_timeout_seconds parameter controls how long to wait; it defaults to the calculated time it would take to fill the pool at the pool’s configured fill rate.
cdp_ws_url for CDP connections and browser_live_view_url for live viewing.
Timeout behavior
Browsers remain in the pool indefinitely until acquired. Once acquired, the pool’stimeout_seconds applies just like a regular browser timeout—if the browser is idle (no CDP or live view connection) for longer than the timeout, it is destroyed and not returned to the pool. The pool will automatically create a replacement browser at the pool’s configured fill rate.
Release a browser
When you’re done with a browser, release it back to the pool. By default, the browser instance is reused. Setreuse: false to destroy it and create a fresh one.
Update a pool
Update the pool configuration. By default, all idle browsers are discarded and rebuilt with the new configuration.The
size parameter is always required when updating a pool, even if you only want to change other settings.discard_all_idle: false to keep existing idle browsers and only apply the new configuration to newly created browsers.
Flush idle browsers
Destroy all idle browsers in the pool. Acquired browsers are not affected. The pool will automatically refill with the pool’s specified configuration.Get pool details
Retrieve the current status and configuration of a pool.List pools
List all browser pools in your organization.Delete a pool
Delete a browser pool and all browsers in it. By default, deletion is blocked if browsers are currently acquired. Useforce: true to terminate acquired browsers and force deletion.
Full example
This example creates a pool with a capacity of 50 browsers and a fill rate of 20 browsers per minute.Understanding fill rate
Thefill_rate_per_minute controls how quickly the pool creates new browsers. With a capacity of 50 and a fill rate of 20:
- Initial fill: The pool takes approximately 2.5 minutes to reach full capacity (50 browsers ÷ 20 per minute)
- After releasing with
reuse: false: If you acquire and release all 50 browsers withreuse: false, each browser is destroyed and a fresh one is created at the fill rate. Replenishing all 50 browsers takes approximately 2.5 minutes. - After releasing with
reuse: true: The browser is immediately returned to the pool and available for the nextacquirecall—no wait time.