Skip to main content
Fetch sends requests directly by default. Enable Browserbase’s proxy network to route requests through a different IP address when a site blocks direct requests, or choose a location to retrieve region-specific content and pricing.

Using proxies

If a site blocks your request or returns a 403 status code, set proxies: true.
Node.js
Enabling proxies may increase response time. If speed is critical and the target site doesn’t require a proxy, leave this disabled.

Targeting a geolocation

To route the request from a specific location, pass proxies as an object with a geolocation. This is useful for fetching region-specific content or pricing. Omit geolocation (or set proxies: true) to use the default exit location.
Node.js
The geolocation object accepts:
Unlike browser sessions, Fetch supports a single Browserbase-managed proxy configuration only. Custom (bring-your-own) proxies and per-domain proxy rules aren’t available on Fetch.

Authenticated Fetch

Fetch pages that require a login with saved browser session state.

Fetch

Return page content without an interactive browser session.