When to use
Use advanced options when you need to:- Control referrer behavior: Set realistic referrers to bypass referrer-based gating
- Accept non-200 responses: Treat specific status codes as successful
- Switch to HTTP/2: Required by some modern sites for correct responses
- Persist sessions: Reuse the same browser session across requests
- Tag requests: Attach a label for tracking or analytics
- Emulate devices: Render pages as mobile or tablet instead of desktop
These are advanced parameters. Misconfiguring them can cause requests to fail
or trigger anti-bot detection.
Parameters
referrer_type
referrer_type
Referrer policy for the request. Nimble sends the chosen referrer header with the request to mimic real browsing behavior.Generic policies:
random- Use a randomly selected referrerno-referrer- Do not send any referrersame-origin- Use the target site’s own origin as referrer
google,bing- Search engine referrersfacebook,twitter,instagram- Social platform referrers
expected_status_codes
expected_status_codes
http2
http2
session
session
Persist a browser session across multiple requests. Useful for maintaining login state, cookies, or navigation context between calls.Fields:
id(string) - Session identifier. Reuse the same ID across requests to share the session.timeout(number) - Session timeout in seconds. Must be greater than 0.retry(boolean, defaultfalse) - Retry the request within the same session on failure.prefetch_userbrowser(boolean, defaultfalse) - Preload the user browser for faster subsequent requests.
tag
tag
request_timeout
request_timeout
Usage
Set a referrer
Send a Google referrer to mimic search engine traffic.Accept multiple status codes
Treat200, 201, and 204 all as successful responses.
Force HTTP/2
Force the request to use HTTP/2 instead of HTTP/1.1.Persist a session
Reuse a browser session across multiple requests.Tag a request
Attach a label to the request for tracking.Set a wait strategy
Control when Nimble considers the page ready with await_for_navigation browser action:
Limit request time
Cap how long Nimble waits for the request withrequest_timeout (milliseconds):
Emulate a device
Render the page as a mobile device.Related
Custom Headers & Cookies
Send custom request headers and cookies
Geo-Targeting
Route requests through specific countries, states, or cities
Stealth Mode
Bypass anti-bot detection with real user emulation
JS Rendering
Render JavaScript-heavy pages before extraction