Skip to main content
Nimble Fast SERP is a realtime API that returns live Google search results as structured data. Submit a query and get back organic listings, pagination, and related questions, parsed and typed at low latency with high success rates.
Fast SERP is available at POST /v2/fast-serp and through all Nimble clients — Python, TypeScript, Go, and the CLI.

Fast SERP SLA

Default SLA and limitations for Fast SERP API
Need higher throughput? Fast SERP scales up to 1,000 QPS. Contact Sales to discuss your requirements.

Quick Start

Example Request

Example Response

How it works

1

Provide a query and search engine

Supply the search query, target engine (google_search), and optional geo-targeting
2

Nimble runs the search

Runs via Nimble’s low-latency infrastructure with geo-targeting applied, no rendering delays, no blocking
3

Results returned as structured data

Data is returned as parsed entity arrays under data.parsing.entities, with optional raw HTML when "html" is included in formats

Parameters

string
required
The search engine to query.
string
The search query string. Required for google_search, google_news, and google_images.Example: "NBA Allstars 2026"
string
Location context for the search. Accepted for google_search and google_images.You can pass either:
  • A location string: Nimble resolves it to the corresponding UULE value (e.g. "United States", "New York, NY")
  • A raw UULE value: Google’s encoded location parameter (e.g. "w+CAIQICIiChIJOwQ...")
Examples:
  • "United States"
  • "London, England"
integer
default:"10"
Number of results to return. Supported on google_search.
integer
default:"1"
Results page to fetch. Combine with num_results to page through results beyond the first batch.
boolean
default:"true"
Whether to return parsed, structured entities. Disable to receive raw HTML only.
boolean
default:"false"
Enable JavaScript rendering for the results page. Disabled by default for lowest latency.
string
Emulate a specific device type. Supported on google_search and google_images.If omitted, defaults to desktop.

Search Engines

Returns organic web results, pagination, related questions, top stories, answer boxes, and more. Supported parameters:
  • query — search query string (required)
  • num_results — number of results to return, 1–100, default 10
  • page — results page for fetching beyond the first batch
  • location — physical location context (string or raw UULE value)
  • device — emulate a specific device type (mobile)
  • parse — return parsed entities (default) or raw HTML only
cURL

Google News

Returns recent news articles matching the query, sourced from Google News. Supported parameters:
  • query — search query string (required)
  • parse — return parsed entities (default) or raw HTML only
Pagination not supported. The location parameter has no effect on this engine.
cURL

Google Images

Returns image results for a query, including image URLs, titles, and source pages. Supported parameters:
  • query — search query string (required)
  • page — results page for fetching beyond the first batch
  • location — physical location context (string or raw UULE value)
  • device — emulate a specific device type (mobile)
  • parse — return parsed entities (default) or raw HTML only
cURL

Response

All responses share the same top-level envelope:

Entities by engine

OrganicResult: one entry per web resultAnswerBox: featured snippet at the top of resultsRelatedQuestionRelatedSearchPagination
NewsResults: the full news results object
ImageResult: one entry per image

Async & Batch Requests

Fast SERP is a realtime-only endpoint. For asynchronous delivery, batching, webhooks, or cloud-storage output, use the SERP API (POST /v2/serp/async, POST /v2/serp/batch) — same engines and parsed entities, with the full delivery toolkit.

Pagination

google_news does not support pagination.
1

Pull up to 100 results in one request

Set num_results: 100 to get up to 100 organic results in a single call. For most use cases, this eliminates pagination entirely.
cURL
2

Need more than 100? Add page to fetch the next batch

Combine num_results: 100 with page to pull 100 results at a time beyond the first batch. Increment page by 1 for each subsequent batch.
cURL
page: 2 → results 101–200, page: 3 → results 201–300, and so on.

Limitations

Next steps

API Reference

Full API reference for the Fast SERP endpoint

Extract

Extract structured content from any result URL