POST /v1/session/{session_id}/request
Request: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 ownfetch() 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 Policyconnect-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:
Separate cookie jars
By default every request and navigation in a session shares one cookie jar, so one session serves one signed-in account. Pass acontext 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:
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.