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
  • Merge Dynamic Parsers
  • Benefits
  • Request Options
  1. Nimble SDK
  2. Web API
  3. Nimble Web API Functions
  4. Data Parsing

Merge Dynamic Parser

Merge Dynamic Parsers

The "Merge Dynamics" feature in Nimble's Web API provides users with the ability to seamlessly integrate Nimble's AI-powered parsing with custom parsing logic into a single, unified response.

This feature is particularly useful for advanced use cases where the out-of-the-box AI parsing might need further refinement, customization, or additional context provided by user-defined parsing rules. By combining both AI and custom parsing, users can achieve a more accurate and tailored data extraction process.

Benefits

  • Enhanced Flexibility: Users can extend and customize the default AI parsing to meet specific data requirements, ensuring that all necessary information is captured in one go.

  • Unified Output: The merging of AI and custom parsing ensures that the final output is consistent, organized, and ready for further processing or analysis.

  • Improved Accuracy: By adding custom parsing, users can refine the data extraction process to capture niche or specialized information that might be missed by general AI parsing.

Request Options

Parameter
Required
Description

parser

Required as true (default = false)

Enum: true | false True - the page's content will be parsed and returned in a JSON format. False - Response will include page headers and raw data (without parsing).

parse_options

Required to enable merge dynamic feature

Object | For advanced parsing options such as merge_dynamic

parse_options.merge_dynamic

Required as true (default = false)

Bool | when set to true, the custom parser results would merge into the AI parsing results under new entity named DynamicEntity

parser

Required

Object | The custom parser template to be merge

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.yelp.com/biz/7-eleven-pembroke-pines-7",
    "country": "US",
    "parse": true,
    "render": true,
    "parse_options": {
        "merge_dynamic": true
    },
    "parser": {
        "YelpBusiness": {
            "selectors": ["html"],
            "type": "object-list",
            "fields": {
                "business_id": {
                    "selectors": [
                        "meta[name='yelp-biz-id']"
                    ],
                    "extractor": "[content]"
                }
            }
        }
    }
}'

Example Response

  • The merged results of the custom parser could be found under DynamicEntity entity

{
    ...
    "parsing":
    {
        "entities":
        {
            "BreadcrumbList": [...],
            "DynamicEntity":
            [
                {
                    "YelpBusiness":
                    [
                        {
                            "business_id": "Z6VUesj0B7wJX3_yqKKPgA"
                        }
                    ],
                    "entity_type": "Dynamic"
                }
            ],
            "ItemList": [...],
            "LocalBusiness": [...]
        },
        "total_entities_count": 6,
        "entities_count":
        {
            "BreadcrumbList": 3,
            "DynamicEntity": 1,
            "ItemList": 1,
            "LocalBusiness": 1
        },
        "metrics":
        {}
    }
}
PreviousParsing TemplatesNextCustom Headers & Cookies

Last updated 8 months ago