The official Postman collection for Reserp, a Google Search API for developers and AI agents. Retrieve visible Google Search result blocks as structured JSON through one stable API.
\nreserp_api_key to your API key. Do not share or publish that value.Requests use bearer authentication. The collection sends Authorization: Bearer automatically. Keep API keys in Postman Vault or a local variable value; never commit or publish them.
Each result block may contain text, url, and children. text is optional: it is omitted when the block has no visible text. When present, it is a non-empty string containing visible text joined with newlines.
Submit a complete https://www.google.com/search URL in the JSON body. Standard Google parameters such as q, gl, hl, tbm, and tbs pass through unchanged. The num parameter is unsupported. If present, start must be 0 or a non-negative multiple of 10.
Pagination uses Google's organic-result offset, not the number of URLs in results. A response can contain URLs from many visible result types—including organic listings, news, carousels, sitelinks, and nested result blocks—so never derive the next offset from results.length.
Omit start or use 0 for the first page, 10 for the second, 20 for the third, and continue in increments of 10. Any other value returns a non-billable 400 invalid_request response.
Clients fetching pages independently or asynchronously can set start directly. pagination.nextUrl is provided as a convenience for clients advancing sequentially from a completed response.
Postman is useful for exploring and testing the API. For bulk or sustained searches, call the API from workers behind a durable queue and control concurrency, retries, and backoff in your application.
\nRetry only when retryable is true. For 429, wait for the number of seconds in Retry-After. For other retryable errors, use exponential backoff with jitter. billed only confirms whether billing settled before the error response; it does not override retryable. A search_failed response can therefore have both retryable: true and billed: true.
Submit a complete Google Search URL and receive visible result blocks in Google's response order.
\nThe URL must use https://www.google.com/search and include a non-empty q parameter. The num parameter is unsupported. If present, start must be 0 or a non-negative multiple of 10. Other Google URL parameters pass through unchanged.
A result block's text field is optional and is omitted when the block has no visible text. When present, text is a non-empty string containing visible text joined with newlines.
Successful responses include billed, which confirms that billing settled by charging prepaid balance or consuming Free allowance. Error responses use the same field to indicate whether billing settled before the error response. Retry only when retryable is true; billed does not override it.
Pagination uses Google's organic-result offset rather than the number of URLs in results. Clients fetching pages independently or asynchronously can set a valid start value directly. pagination.nextUrl is an optional convenience for sequential clients; never derive the next offset from results.length.