September

Nimble SDK Feature Updates

State & City geo-targeting via Nimble API

Description

Geo-targeting by City and State is now available via Nimble APIs. Previously exclusive to proxy users, this functionality is now accessible across all API endpoints with the new city and state parameters, in addition to the country parameter.

Available in Web, SERP, Maps and eCommerce APIs
For more information, read related documentation.

Example Request

include the state and city fields in your API request. Make sure to refer to the list of supported locations provided by Nimble IP. For example:

curl --location --request POST 'https://api.webit.live/api/v1/realtime/web' \
--header 'Authorization: Basic <Token>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "url": "https://ipinfo.io/json",
    "country": "US",
    "state": "NY",
    "city": "brooklyn",
    "render": true
}'

Blocked Domains for Resource Loading

Description

Webpages typically load resources from many external domains, including iframes, images, javascript files, and other resources. In some cases, it may be beneficial to restrict non-essential resources in order to speed up the loading of a page, save bandwidth, and more.

This feature allow the user to prevent the external resources of a certain domains from being loaded while page is rendered, with the new blocked_domains parameter in render_options. This helps manage and block unwanted resources during page rendering

Available in Web API.
For more information, read related documentation.

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",
    "method": "GET",
    "parse": true,
    "render": true,
    "render_options": {
        "include_iframes": true,
        "blocked_domains": ["example2.com", "example3.com"]
    }
}'

Website Cookies Collection

Description

Websites may set cookies for a variety of purposes, from identifying returning users to storing user preference information.

Capture dynamic cookies set by websites after page load with the new get_cookies parameter in render_flow. This allows you to collect cookies used for user identification and preferences.

Available in Web API.
For more information, read related documentation.

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",
    "render": true,
    "render_flow": [{
        "get_cookies": {
                "timeout": 1000
        }
    }]
}'

Screenshot Format Support

Description

We’ve expanded our screenshot format options. Alongside the default PNG, you can now choose between PNG and WEBP base64 formats using the new format parameter in render_flow.screenshot

Available in Web API.
For more information, read related documentation.

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",
    "render": true,
    "render_flow": [{
        "screenshot": {
                "full_page": true,
                "format": "jpeg",
                "timeout": 30000
        }
    }]
}'

Google News Tab in SERP API

Description

Google News Tab in SERP API: This feature allows users to directly access news-specific search results through the SERP API. By using the new tab parameter, you can specify that you want to retrieve results from the News tab in Google Search.

This is achieved using the standard Google Search URL format (e.g., www.google.com/search?q=olympics+2024&tbm=nws), rather than relying on news.google.com. This approach ensures more consistent and comprehensive news results directly from Google’s main search engine.

Available in SERP API.
For more information, read related documentation.

Example Request

curl -X POST 'https://api.webit.live/api/v1/realtime/serp' \
--header 'Authorization: Basic <credential string>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "search_engine": "google_search",
    "country": "US",
    "query": "Sample search phrase",
    "tab": "news"
}'

Ads Optimization in SERP API

Description

This feature helps to increase the visibility of paid results (sponsored ads) in Google Search. It introduces a new Boolean parameter named ads_optimization, which enables users to optimize the number of ads returned.

The feature operates in "incognito mode" to avoid personalization and ensure the results are based solely on the ad content rather than user-specific search history.

Available in SERP API.
For more information, read related documentation.

Example Request

curl -X POST 'https://api.webit.live/api/v1/realtime/serp' \
--header 'Authorization: Basic <credential string>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "search_engine": "google_search",
    "country": "US",
    "query": "Sample search phrase",
    "ads_optimization": true
}'

Google Maps Reviews Sorting in Maps API

Description

This feature introduces the ability to specify the sorting method for reviews when using the Google Maps reviews endpoint. A new parameter named sort is added to the google_maps_reviews search engine, allowing customers to choose how reviews are sorted.

The sort parameter is an enum with multiple options: relevant, newest, highest_rating, and lowest_rating. This allows clients to sort the returned reviews based on their preference.

Available in Maps API.
For more information, read related documentation.

Example Request

curl -X POST 'https://api.webit.live/api/v1/realtime/serp' \
--header 'Authorization: Basic <credential string>' \
--header 'Content-Type: application/json' \
--data-raw '{
    "search_engine": "google_search",
    "country": "US",
    "query": "Sample search phrase",
    "ads_optimization": true
}'

Direct Access to XHR Requests

Description

We now support scraping internal XHR calls directly by passing them as the target URL with render set to false. Previously, network capture (with render set to true) was required for XHR data extraction. Use the new is_xhr Boolean parameter to specify if the target page is an XHR request.

Available in Web API.
For more information, read related documentation.

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.lowes.com/wpd/5001374857/productdetail/1875/Guest",
    "country": "US",
    "is_xhr": true
}'

Previous2024 NextOnboarding Guide

Last updated 3 months ago