A real-time request allows users to collect data from the search of a single search term. The collected data is returned directly to the user performing the request. The Nimble SERP API currently supports the following search engines:
To send a request, use the /realtime/serp endpoint with the following syntax:
Nimble APIs requires that a base64 encoded credential string be sent with every request to authenticate your account. For detailed examples, see Web API Authentication.
String | LCID standard locale used for the URL request. Alternatively, user can use auto for automatic locale based on country targeting.
location
Optional
String
Search Google through a custom geolocation, regardless of country or proxy location. eg: "London,Ohio,United States". See Getting local data for more information.
parse
Optional (default = true)
Boolean
Instructs Nimble whether to structure the results into a JSON format or return the raw HTML.
ads_optimization
Optional (default = false)
Boolean
This flag increases the number of paid ads (sponsored ads) in the results. It works by running the requests in 'incognito' mode (requires JS rendering)
Jan 25: Due to latest Google changes, the ads_optimization flag requires JS rendering which forces the request to use VX8 Driver and hence increase the request's computing costs.
Response
Headers
X-Task-ID: string
Payload examples:
If parsing is disabled, the resulting data will be the raw HTML of the requested SERP. If parsing is enabled, a JSON object with a parsed version of the SERP will be delivered in addition to the raw HTML, which is contained under the html_content property.