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
        • 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
    • 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: longer, stickier, more accurate sessions
        • Using IPv6 Proxies
        • 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
    • LangChain Integration
  • 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
    • Deprecated APIs
      • E-commerce API
        • E-commerce API Authentication
        • Real-time product request
        • Real-time product search request
        • Delivery methods
        • Batch Processing
        • Endpoints and Response Codes
      • Unlocker Proxy Overview
        • Unlocker Proxy Quick Start Guide
          • Real-time request
          • FAQs
        • Unlocker Proxy FAQ
Powered by GitBook
On this page
  • Web API Browserless Drivers
  • Why?
  • How?
  • Drivers Optimization Engine
  • Driver Parameter in API Responses
  1. Technologies

Browserless Drivers

PreviousLangChain IntegrationNextAPI Driver-Based Pricing

Last updated 3 months ago

Web API Browserless Drivers

Nimble Web API's capabilities are powered by a range of specialized Browserless Drivers, each optimized for specific types of data gathering & automation tasks. These drivers allow you to overcome various challenges and efficiently retrieve data from different types of web pages:

Driver
Rendering?
Use Case
Complexity

VX6

No

Fast Native Requests

Low

VX8

Yes

Javascript Rendering

Medium

VX10

Yes

Stealth Undetection

High

VX12

Yes

Social Media Platforms

High

VX12-PRO

Yes

Person Data (LinkedIn)

High

Each of these Drivers uses a unique strategy (AI Fingerprinting, User Behavior Emulation, and more) to overcome a particular type of obstacle. Nimble's determines the type of data source in real-time for each request, and automatically deploys the most suitable driver:

  • Built from the ground-up by Nimble Labs AI experts for data collection purposes.

  • Utilizes multiple advanced stealth undetection capabilities to ensure successful data collection.

  • Smart engines include human behavior emulation, synthetic fingerprinting, and more.

  • Capable of rendering web pages as a real browser would, including executing JavaScript and AJAX calls, to access dynamically loaded data.

  • Offers seamless integration with Nimble's IP Residential Proxies to access geo-restrictions and IP rate limits, ensuring uninterrupted access to global web data.

VX6 - Native Driver

What? Optimized for handling straightforward native queries that do not require page rendering.

When? Best used for fast native requests where page rendering is unnecessary. Ideal scenarios like retrieving Google SERP data quickly and cost-efficiently.

VX8 - Rendering Driver

What? Suitable for scenarios needing basic page rendering and undetection capabilities, offering a balance between performance and complexity.

When? Perfect for client-side rendered websites, single-page applications (SPAs), and other webpages that require rendering to retrieve data, whether via HTML or network capture. Best suited for low to mid-level websites in terms of complexity, load, and access challenges measures.

VX10 - Advanced Website Access

What? Our most advanced option, designed for unlocking complex rendering tasks and equipped with advanced features to access websites effectively.

When? Ideal for the most challenging and complex use cases, supporting the most sophisticated stealth undetection capabilities and backend technologies stack at scale.

VX12 - Social Media Driver

What? A dedicated driver specifically designed to retrieve data from popular social media platforms.

When? Best used for extracting data from Instagram, Facebook, LinkedIn, and Twitter.

  • Available only when using Social API Endpoint

VX12-PRO - Person Data Driver

What? A specialized driver for retrieving detailed information from LinkedIn profiles.

When? Exclusively used for extracting multiple data points from LinkedIn profiles.

  • Available only when using Person API Endpoint

Why?

How?

Drivers Optimization Engine

Nimble API is powered by an intelligent Optimization Engine that automatically selects the most appropriate Browserless Driver for your task. This AI engine evaluates the target domain and use case to determine the most cost-effective and performance-optimized driver, ensuring efficiency and effectiveness in website access & data retrieval.

This process not only simplifies the decision-making process but also ensures that you’re using the right tool for the job every time.

  • Subscribed users in Enterprise Plan have the flexibility to manually select a specific driver if desired, but by default, the system will auto-select the most suitable driver to ensure optimal results.

  • Users in Other Plans cannot select the driver selection and have limited access to VX10 Driver (up to 10%)

The Web API supports manual selection of drivers (VX6, VX8, VX10), while the Social API automatically configures its drivers (VX12, VX12-PRO) across all endpoints. Therefore the VX12, VX12-PRO Drivers cannot be used with Web API endpoints.

Driver Parameter in API Responses

  • The driver parameter is included in every API request response, whether it is selected manually or by the optimization engine.

  • This parameter provides transparency on which driver was used per request. Driver distribution will soon be available in the Nimble App.

Drivers Optimization Engine