Skip to main content
Advanced options let you control how Nimble issues requests at a lower level. Use them to tune referrer behavior, accept specific response codes, switch protocols, persist sessions, tag requests, or emulate different device types.

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

string
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 referrer
  • no-referrer - Do not send any referrer
  • same-origin - Use the target site’s own origin as referrer
Search and social referrers:
  • google, bing - Search engine referrers
  • facebook, twitter, instagram - Social platform referrers
Example:
array
HTTP status codes that should be treated as successful. By default, only 200 is considered success. Use this to accept responses like 201 (Created), 204 (No Content), or 302 (Redirect).Format: Array of integers.
Example:
boolean
default:"false"
Use HTTP/2 instead of HTTP/1.1 for the request. Some sites require HTTP/2 to return the expected response.
Example:
object
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, default false) - Retry the request within the same session on failure.
  • prefetch_userbrowser (boolean, default false) - Preload the user browser for faster subsequent requests.
Example:
string
User-defined label attached to the request. Use tags to group requests by campaign, workflow, or customer for tracking and analytics.
Example:
number
Maximum time in milliseconds to wait for the request to complete. Increase for slow or JS-heavy pages; decrease to fail fast on unresponsive targets.
Example:
string
default:"desktop"
Device type for browser emulation. Affects viewport size, user agent, and rendering behavior.Options: desktop | mobile | tablet
Example:

Usage

Set a referrer

Send a Google referrer to mimic search engine traffic.

Accept multiple status codes

Treat 200, 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 a wait_for_navigation browser action:

Limit request time

Cap how long Nimble waits for the request with request_timeout (milliseconds):

Emulate a device

Render the page as a mobile device.

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