Public URL or domain to fetch. Bare domains default to HTTPS; explicit HTTP and HTTPS URLs are preserved.

Browser navigation state when the browser path is selected: load, domcontentloaded, networkidle, or commit.

CSS selector to wait for after navigation. Use this for pages that render content after the initial load.

CSS selector to scroll into view after navigation. Use it to trigger lazy-loaded feeds, comments, and media before wait_ms and network capture.

Extra fixed wait after navigation, in milliseconds. Capped by timeout_ms. Use only when there is no reliable selector.

Navigation and selector timeout in milliseconds. Maximum 240000. The default is deliberately generous so the first call after a cold browser start has room to finish.

Optional short-lived in-process response cache TTL for identical synchronous fetch payloads. Range 0-60000. Hits are best effort per API worker; the cache key ignores cache_ttl_ms itself.

Execution strategy. auto uses direct HTTP for simple body/JSON fetches and Chromium when the payload asks for browser-only features or the fast path looks blocked. http returns the raw HTTP response without browser-only features. browser forces the rendered browser path.

Include the raw response body in body_text. JSON responses include it automatically. When set with an API-shaped URL (a path with no .html/.php-style extension), this also participates in auto strategy selection and can auto-select browser JSON mode — unless screenshot, full_page, or wait_selector is also set, which keeps the request on the rendered-page path. Site-root URLs with no path (https://example.com) are always treated as pages, never APIs.

Include rendered/raw HTML in html. Set false for JSON/body workflows to reduce response size and skip origin DOM serialization in browser JSON mode.

Attempt to collect Cloudflare cf_clearance token data and return it when the browser receives that cookie. When false, cookies are not read or returned.

Attempt to collect DataDome datadome cookie data and return it when the rendered browser session receives that cookie. When false, DataDome cookie fields are not read or returned.

Return storage-ready cookies visible to the final rendered page in cookies.

Preload cookies into the browser context before navigation. Each cookie needs name and value plus either url or domain; path defaults to / when domain is used.

Capture matching browser network calls and return them in network. Defaults to XHR/fetch only — useful for API discovery and debugging.

Playwright resource types to capture, e.g. xhr, fetch, document, script, or websocket. Keep this narrow for most workloads.

Include capped response bodies for captured network responses.

Include request and response headers for captured entries. Off by default because headers can contain cookies, bearer tokens, or other secrets.

Maximum matching network entries to return. Range 1–500.

Maximum bytes kept from each captured response body. Range 0–1048576.

When capture_network is true, capture streamed fetch/XHR chunks, EventSource messages, and WebSocket messages in network_streams.

Maximum streamed network values to return. Range 1–500.

Maximum bytes kept from each streamed network value. Range 0–262144.

Include a PNG screenshot encoded as base64. Works together with return_response_text: requesting a screenshot keeps the request on the rendered-page path, so both come back. Only explicit json_mode: true disables screenshots. Screenshots can make responses much larger, so request them only when needed.

Capture the full scrollable page when screenshot is true.

Two-letter country code for browser geo-emulation, e.g. us, gb, de, au, ca. When geoip is true and locale/timezone are unset, Better Fetch applies representative browser defaults for that country. This does not change network egress IP.

Pro/Scale network routing. none uses Better Fetch datacenter egress. auto starts direct and escalates blocked retries through residential egress. residential routes every attempt through residential egress. When country is also set, proxied attempts use that country for the exit and browser identity. Each residential attempt that occurs costs 25 credits.

Account-scoped browser identity key. Reuse it to keep the same warm browser context, fingerprint, cookies, localStorage, and encrypted portable snapshot. Only letters and numbers form the canonical key today, so punctuation is ignored.

When country is set, apply country-derived browser timezone/locale defaults unless explicit locale/timezone values are supplied. This does not spoof WebRTC IP or change network egress IP.

Browser locale, e.g. en-GB. Overrides the country-derived locale.

Browser timezone, e.g. Europe/London. Overrides the country-derived timezone.

Custom user agent applied to the browser context. Usually leave unset — it forms part of a session's warm-context identity.

Additional HTTP headers applied to the direct HTTP request or inside the browser context.

Human-like mouse, keyboard, and scroll behavior for browser fetches. Defaults to true for rendered browser pages and false for direct/API calls. Set explicitly to override.

Fetch via an in-page browser fetch() call instead of a top-level browser navigation. Sends Sec-Fetch-Mode: cors and a natural Referer from the URL's origin. Auto-detected from Accept: application/json or from return_response_text on an API-shaped URL — but never when screenshot, full_page, or wait_selector is set (those signal a rendered page), and never for site-root URLs with no path. An explicit true/false always wins; note screenshots are unavailable in json_mode.

true when Better Fetch completed the request — not whether the target accepted it. Check status and blocked for the target's verdict.

HTTP status from the target response (navigation or in-page fetch). On challenge-fronted sites this can be stale: after Better Fetch observes a challenge clear, the solved page can render while status keeps the original 403/503. Use blocked, not status alone, as the browser-fetch outcome signal.

Final target URL after redirects.

Page title after rendering, or the parsed title for direct HTTP HTML responses.

Rendered DOM HTML from the browser, or raw HTML from the direct HTTP transport. Empty when include_html is false.

Raw response body when requested, when the target response is JSON, or when strategy=http. Capped at 50 MB — see body_truncated.

Total response body size in bytes when measured by a body-fetch strategy. When body_truncated is true, this is larger than body_text.length.

True when the response body exceeded the 50 MB transfer cap and was truncated. Reduce per_page or narrow the query if you need the complete body.

Normalized response Content-Type media type without parameters, for example text/html or application/json. Empty when unavailable.

Best-effort response body category for routing parser logic.

Whether body_text parsed as JSON.

Parsed JSON payload when json_parse_ok is true; otherwise null.

Response headers from the target navigation response (string values).

Base64-encoded PNG when screenshot is true; otherwise null. Always null in json_mode — in-page fetch() never renders the target as a page, which is why screenshot: true suppresses json_mode auto-detection.

Cloudflare cf_clearance token value when return_cf_clearance is true and the target issued it.

Storage-ready cookie metadata (name, value, domain, path, expires, httpOnly, secure, sameSite) when requested and present.

The session that produced the clearance result. Blocked retries may rotate to a fresh session before the final result.

DataDome datadome cookie value when return_datadome_cookie is true and the target issued it. Otherwise null or omitted.

Storage-ready datadome cookie metadata when requested and present. Otherwise null or omitted.

The session that produced the DataDome cookie result. Blocked retries may rotate to a fresh session before the final result.

Present when return_datadome_cookie is true. true when the rendered page or response showed DataDome signals, even if no datadome cookie was returned.

Storage-ready cookies visible to the final rendered page when return_cookies is true. Otherwise omitted.

Captured browser network entries when capture_network is true. Otherwise omitted.

Captured streamed fetch/XHR chunks, EventSource messages, and WebSocket messages when network_capture_streams is true. Otherwise omitted.

true when the response looks like a bot wall or unsolved challenge — even when the target returns HTTP 200. The inverse also holds: a 403/503 whose rendered body is substantial real content with no live interstitial is a solved challenge and reports blocked: false. Trust blocked over status in both directions.

Stable reason for the blocked verdict. none means the response is not classified as blocked.

Whether the attempt that produced this result ran a headed browser (set on escalated retries).

true when served from a warm pooled context (session requests); false for sessionless ephemeral contexts.

Execution transport that produced the result.

Synchronous fetch cache status. bypass means no cache was requested or enabled; miss means the target was fetched; hit means a completed prior result was reused; coalesced means an identical in-flight fetch was shared.

Total attempts including the first. Greater than 1 means the service retried on a fresh session — after a block or a transient navigation timeout.

Whether the final attempt used managed residential egress.

Residential attempts that actually occurred. Cache hits and coalesced followers have no billable proxy attempts.

Total charged credits. Ordinary retrieval is 1; each actual residential attempt is 25 credits.

Remaining period credits after a residential post-charge, when available.

Time spent inside the fetch request (final attempt).

true when the job was found and belongs to the authenticated account.

Job identifier (UUID).

Current job state: queued, running, done, or failed.

Full FetchSuccess payload (same shape as POST /v1/fetch) when status is done; otherwise null.

Error message when status is failed; otherwise null.

ISO timestamp when the job was admitted.

ISO timestamp when the browser work began.

ISO timestamp when the job reached done or failed.

ISO timestamp after which the job result is cleaned up (24 hours after creation by default).