Skip to main content
Send an arbitrary HTTP request through the session’s own Chrome, sometimes called browser-curl. The request carries the browser’s cookies, its TLS and HTTP/2 fingerprint, and the session’s exit IP, so it is indistinguishable from a request the page itself would make. The common use is replaying a site’s own API, the JSON or GraphQL endpoint its front end calls, once a page on that origin has loaded. The request runs in the session’s current tab, so navigate to the site first, then call the site’s API with the cookies that page holds.

POST /v1/session/{session_id}/request

Request:
Response (200):
The body comes back as UTF-8 text for textual content types, otherwise base64 with bodyEncoding: "base64".

Billing

The request bills the response bytes as egress at the session’s exit tier (datacenter, ISP, residential or your own proxy), and the open session bills browser time as usual. There is no per-request fee.

Parallel requests

Requests on one session run concurrently. Fire many at once and the browser issues them in parallel, as a page’s own fetch() does. One exception is outside our control: Chrome coalesces several in-flight requests to the exact same URL into one, so a burst of identical URLs still returns one at a time. Give each a distinct URL (a cache-busting query parameter is enough) when you need identical requests to run in parallel.

Pages that block the request

A page whose Content Security Policy connect-src does not include its own origin blocks a same-origin request made from that page, which answers 502 fetch_failed. Create the session with bypassCSP: true to run it outside the page’s CSP:
The flag is armed before each navigation, so the page loads without CSP enforcement and a later same-origin request is not blocked. It is off by default and scoped to the session. It lifts the page’s CSP only; a cross-origin request with no CORS headers is still an opaque response, as in any browser. By default every request and navigation in a session shares one cookie jar, so one session serves one signed-in account. Pass a context id to run in an isolated browser context with its own jar and storage. Navigate a context to establish its session, then send requests in the same context:
The default context is the session’s main tab and runs the full managed anti-bot ladder on navigation. A non-default context is a plain guarded navigation, meant for holding an account rather than clearing a wall. A session holds up to 32 contexts.