Google Search API

Preview

Google search results in structured JSON, including organic listings, related questions, and rich results when available.

Live requests are not available yet.The endpoint is not configured. Examples use the planned API contract; no requests or credits are used here.

GETEndpoint not configuredJSON response

Playground

Google Web Search

Request example Endpoint placeholder

GOOGLE_SEARCH_ENDPOINT and YOUR_API_KEY are placeholders.

Illustrative response for Coffee in Austin. This example stays fixed when request parameters change.

Quickstart

Create an API key. Manage credentials in API Keys.
Prepare a Google search. Set engine=google and a required q. Add localization or pagination parameters as needed.
Use the published endpoint once available. The request examples above are templates. The Google Search endpoint is currently unconfigured.

Authentication

QueryPilot uses the X-API-Key request header. Use your QueryPilot key, not an upstream provider key. Full keys are shown only when created or rotated.

X-API-Key: YOUR_API_KEY

Keep API keys in server-side environment variables. The examples here contain no account credentials.

Request parameters

Planned parameters for standard Google web search. Availability will be confirmed when the endpoint is connected.

Parameter	Type / default	Description

start=0 selects the first page; 10 selects the next. The number of returned organic results can vary. A num parameter is not included in this preview.

Response reference

Field names, nesting, and JSON types follow the SerpApi Google Search format. Rich result modules are conditional and may be absent for a query.

Field	Type	Content

Organic result

Each item can include position (number), title, link, displayed_link, and snippet (strings). Optional fields include date, source, thumbnail, favicon, snippet_highlighted_words (array), and sitelinks (object). Handle missing optional fields in your client.

Request metadata and links

search_metadata.id will identify the QueryPilot request. Timestamps follow YYYY-MM-DD HH:mm:ss UTC; total_time_taken is measured in seconds. Archive URLs and provider-specific continuation links are not available in this preview. QueryPilot URLs will be documented when those capabilities are implemented.

Errors & billing

This playground does not send search requests and uses no credits. Pricing, billable outcomes, rate limits, and the final error contract will be published with live access.

A response with search_metadata.status = "Success" in the static example is sample data, not a live request status. Clients should eventually check both the HTTP status and the response error fields.

Contact support