Real-time search request
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.
Every request sent through Nimble API is automatically routed through Nimble IP - our premium proxy network!
Request Options
query
Required
String
The term or phrase to search for.
search_engine
Required
Enum: google_search
google_sge
bing_search
yandex_search
The search engine from which to collect results.
tab
Optional (default = null)
Enum:
news
Select the tab of results to return from google_search
engine. Currently, news
is supported.
num_results
Optional
Integer
Set the mount of retuned search results
domain
Optional
String
Search through a custom top-level domain of Google. eg: "co.uk"
country
Optional (default = all)
String
Country used to access the target URL, use ISO Alpha-2 Country Codes i.e. US, DE, GB
state
Optional
String
For targeting US states (does not include regions or territories in other countries). Two-letter state code, e.g. NY, IL, etc.
city
Optional
String
locale
Optional (default = en)
String
String | LCID standard locale used for the URL request. Alternatively, user can use auto
for automatic locale based on country targeting.
location
Optional
String
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.
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.
200 OK
500 Error
400 Input Error
Response Codes
200
OK.
400
The requested resource could not be reached.
401
Unauthorized/invalid credental string
500
Internal service error.
501
An error was encountered by the proxy service.
Last updated