LogoLogo
Nimble HomeLoginCreate an Account
  • Home
  • Quick Start Tutorials
    • Tutorial Library
      • Track SEO and SEM Ranking
      • Reddit as a Guerilla Marketing Strategy
  • Nimble Platform
    • Nimble Platform Overview
    • Online Pipelines
      • Supermarkets
        • ASDA
        • Tesco Groceries
        • Sainsbury’s
        • Morrisons
      • eCommerce
      • Restaurants
        • Yelp
        • Tabelog
        • Uber Eats Japan
        • Demaecan
        • Uber Eats US
      • Real Estate
        • Zillow
  • Nimble SDK
    • SDK Overview
    • Web API
      • Web API Overview
      • API Product Specs
      • Nimble Web API Quick Start Guide
        • Introduction
        • Nimble APIs Authentication
        • Real-time URL request
        • Delivery methods
        • Batch processing
        • Response codes
        • FAQs
      • Nimble Web API Functions
        • Realtime, Async & Batch Request
        • Geo Location Targeting
        • Browserless Drivers
        • Javascript Rendering
        • Page Interaction
          • Wait (delay)
          • Wait for Selector
          • Wait and Click
          • Wait and Type
          • Scroll
          • Scroll to
          • Infinite Scrolling
          • Capturing Screenshots
          • Collecting Cookies
          • Executing HTTP Requests
          • Operation Reference
        • Network Capture
          • Filter by URL Matching
          • Filter By Resource Type
            • Real World Demo: Capturing Ajax Requests
          • Wait for Requests
          • Capturing XHR without Rendering
          • Operation Reference
        • Data Parsing
          • Parsing Templates
          • Merge Dynamic Parser
        • Custom Headers & Cookies
        • General Params
      • Vertical Endpoints
        • SERP API
          • Real-time search request
          • Getting local data
          • Browsing SERP pagination
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
        • Maps API
          • Searching for places
          • Getting information about a place
          • Collecting reviews
          • Delivery methods
          • Batch processing
          • Endpoints and Response Codes
        • E-commerce API
          • E-commerce API Authentication
          • Real-time product request
          • Real-time product search request
          • Delivery methods
          • Batch Processing
          • Endpoints and Response Codes
    • Web Retrieval API
      • Web Retrieval API Overview
    • Proxy API
      • Nimble IP Overview
      • Nimble IP Quick Start Guide
        • Send a request
        • Nimble IP Autentication
        • Geotargeting and session control
        • Response codes
        • FAQs
      • Nimble IP Functions
        • Country/state/city geotargeting
        • Controlling IP rotation
        • Geo-sessions: stickier, location-based sessions
        • Using IPv6 Proxies
        • Unlocker Proxy
        • Response Codes
      • Integration Guides
        • Incogniton
        • Kameleo
        • VMLogin
        • AdsPower
        • FoxyProxy
        • Android
        • Multilogin
        • iOS
        • SwitchyOmega
        • Windows
        • macOS
        • Proxifier
        • MuLogin
        • Puppeteer
        • Selenium
        • Scrapy
    • Client Libraries
      • Installation
      • Quick Start
  • AI Agents
    • LangChain Integration
    • MCP Server
      • Available Tools
  • Technologies
    • Browserless Drivers
      • API Driver-Based Pricing
    • IP Optimization Models
    • AI Parsing Skills
  • Management Tools
    • Nimble Dashboard
      • Exploring the User Dashboard
      • Managing Pipelines
      • Reporting and Analytics
      • Account Settings
      • Experimenting with the Playground
      • Billing and history
    • Nimble Admin API
      • Admin API basics
      • Admin API reference
  • General
    • Onboarding Guide
      • Getting started with Nimble's User Dashboard
      • Nimble IP Basics
      • Nimble API Basics
      • Helpful Resources
    • FAQs
      • Account Settings and Security
      • Billing and Pricing
      • Tools and Integrations
      • Nimble API
      • Nimble IP
Powered by GitBook
On this page
  1. Nimble SDK
  2. Web API
  3. Nimble Web API Functions

Browserless Drivers

PreviousGeo Location TargetingNextJavascript Rendering

Last updated 2 months ago

CtrlK
  • What?
  • Available Drivers (Web API Only)
  • When to Use the driver Parameter
  • What Happens If I Don’t Set It?

Nimble's infrastructure uses specialized Browserless Drivers under the hood to optimize performance, rendering, and access behavior based on your use case. By default, the optimal driver is selected automatically. However, for advanced use cases, you can control which driver to use explicitly in your Web API requests.

What?

Drivers are internal configurations that determine:

  • Whether a headless or headfull browser is used.

  • If rendering, stealth techniques, or anti-bot mitigation is applied.

  • The depth and accuracy of page interaction and data capture.

Nimble's optimization engine intelligently selects the best driver when driver is not set. However, advanced users can specify a driver manually via the Web API endpoint using the driver parameter.

read more on Browserless Drivers here - Browserless Drivers

Note: Driver control is only supported in the Web API. It cannot be set manually in other API verticals.

Available Drivers (Web API Only)

The following drivers are available for explicit use only via the Web API endpoint:

Driver
Rendering
Mode
Description

vx6

❌

Headless

Fastest non-rendering mode for simple page loads and API endpoints.

vx8

✅

Headless

Default headless rendering mode. Best for pages requiring light JS rendering.

vx8-pro

✅

Headfull

Headfull rendering with more human-like behavior. Ideal for moderate anti-bot protections.

vx10

✅

Headless Stealth

Advanced stealth for highly protected websites.

vx10-pro

✅

Headfull Stealth

Highest-grade stealth and realism. Best for heavily fortified targets.

The driver parameter overrides the render flag:

  • render: false = uses vx6 which is the default

  • render: true = uses vx8 or vx10 automatically depending on the domain


When to Use the driver Parameter

  • You want guaranteed behavior for rendering, stealth, or evasion.

  • You’re targeting websites with known protection mechanisms.

  • You need reproducible results across environments.

  • You’re optimizing cost/performance across different types of content.

Example Request

curl -X POST 'https://api.webit.live/api/v1/realtime/web' \
--header 'Authorization: Basic <credential string>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "url": "https://www.example.com",
    "driver": "vx6"
}'

What Happens If I Don’t Set It?

If you omit the driver parameter:

  • Nimble automatically selects the best driver for the domain.

  • The selected driver is returned in the response payload for any API request.

  • You can also view driver usage and history in the Nimble App under your Dashboard or Analytics.