--- title: "Google Search API: Get Search Results as JSON | Perceptlayer" description: "Call GET /v1/google-search/search for organic results as JSON at 1 credit a call. Parameters, a real recorded response and the cost in credits." url: https://perceptlayer.com/blog/google-search-api-json --- [Blog](https://perceptlayer.com/blog) / [API guides](https://perceptlayer.com/blog/category/api-guides) # Google Search API: Get Search Results as JSON 10 Aug 2026 Perceptlayer 7 min read One GET request to `/v1/google-search/search` with a `query` returns Google search results as JSON: organic results with position, title, link and snippet, plus related searches. It costs 1 credit per successful call, and failed calls cost nothing. This matters now because Google's own Custom Search JSON API is closed to new customers. ## Key takeaways - Google's Custom Search JSON API is closed to new customers, and existing customers have until January 1, 2027 to move to something else. - `GET /v1/google-search/search` takes one required parameter, `query`, and returns `organic_results`, `related_searches` and `people_also_search_for` in the recorded response. - Each successful call costs 1 credit, so 1,000 calls cost 1,000 credits; see [pricing](https://perceptlayer.com/pricing) for what credits cost. Custom Search charges $5 per 1,000 queries. - The Google Search API has 7 endpoints, covering standard results, AI Overviews, AI Mode, place details and autocomplete. - You get 1,000 free credits every month after verifying an email address, with no credit card. ## Why does the Custom Search JSON API no longer work for new projects? Google's documentation states that ["the Custom Search JSON API is closed to new customers"](https://developers.google.com/custom-search/v1/overview) and that existing customers have until January 1, 2027 to transition to an alternative. The page points to Vertex AI Search for searching up to 50 domains. If you need results from the open web as JSON, you need a different source. That is a real constraint if you were planning to start on it today. A new project can't get a key, and an old one has a deadline. Google's page also lists the pricing that still applies to current users: 100 queries a day free, then $5 per 1,000 queries, up to 10,000 queries a day. Vertex AI Search is the better fit if your goal is search over a fixed set of your own sites. It is a different product from "give me the results page for this query as JSON". For that job, the rest of this article shows the replacement request. ## How do you get Google search results as JSON? Send a GET request to `https://api.perceptlayer.com/v1/google-search/search` with your query and your key in the `X-API-Key` header. The response is JSON with named fields, not a page of HTML. If you don't have a key yet, [get a free API key](https://perceptlayer.com/signup); the [authentication docs](https://docs.perceptlayer.com/authentication) cover the header and the `api_key` query parameter alternative. ```bash curl "https://api.perceptlayer.com/v1/google-search/search?query=best+restaurants+in+Berlin&hl=en&safe=off" \ -H "X-API-Key: $API_KEY" ``` `hl` sets the interface language and `safe=off` turns off safe search. Both are optional. Only `query` is required. You can also run the same call from the playground on the [Google Search API page](https://perceptlayer.com/apis/google-search): pick the endpoint, fill in the parameters and run it with your key. ## What does the response look like? The recorded response for the request above starts with `search_information`, followed by an `organic_results` array. Each entry carries the fields below, taken from the recorded output. The excerpt is trimmed with `…`. ```json { "search_information": { "query_displayed": "best restaurants in Berlin", "organic_results_count": 6 }, "organic_results": [ { "position": 1, "title": "The Best Restaurants in Berlin - Food Guide & Map", "link": "https://andershusa.com/best-restaurants-berlin-germany-guide/", "displayed_link": "https://andershusa.com › best-restaurants-berlin-german...", "snippet": "Dec 3, 2025 — Tim Raue is the most internationally renowned restaurant in Berlin. It holds two Michelin stars, has been frequently ranked on The World's 50 ...", "snippet_highlighted_words": [ "Tim Raue is the most internationally renowned restaurant in Berlin" ], "source": "Anders & Kaitlin", "rank_group": 1, "rank_absolute": 4 }, … ], "related_searches": [ { "query": "Best restaurants in Berlin for tourists", "link": "https://www.google.com/search?safe=off&gl=us&hl=en&complete=0&pws=0&nfpr=1&q=Best+restaurants+in+Berlin+for+tourists" }, … ], "people_also_search_for": [ { "name": "Best restaurants in Berlin for tourists", "query": "Best restaurants in Berlin for tourists", "link": "https://www.google.com/search?safe=off&gl=us&hl=en&complete=0&pws=0&nfpr=1&q=Best+restaurants+in+Berlin+for+tourists" }, … ], … } ``` The recorded response also includes a `redirect_link` on each organic result, which we cut from the excerpt for length. | Field | What it holds | | --- | --- | | `search_information.query_displayed` | The query as the results page displayed it | | `search_information.organic_results_count` | A count of organic results (6 in this recording) | | `organic_results[].position` | The result's position in the organic list | | `organic_results[].title`, `link`, `snippet` | The heading, destination URL and text snippet | | `organic_results[].displayed_link` | The shortened URL shown under the title | | `organic_results[].source` | The site name shown for the result | | `organic_results[].rank_group`, `rank_absolute` | Rank within the organic group, and the absolute rank on the page | | `related_searches[]`, `people_also_search_for[]` | Suggested follow-up queries with their links | Note the difference between `position` and `rank_absolute`. In the recording, the first organic result has `position` 1 and `rank_absolute` 4, so the two fields measure different things. If you track rankings, store both. ## Which parameters does the search endpoint take? `GET /v1/google-search/search` takes one required parameter, `query`, and a long list of optional ones for location, language, filters and paging. The ones most readers need are in the table below. Allowed values come from the endpoint's parameter list; no defaults or page sizes are documented, so don't assume any. | Parameter | Type | What it does | | --- | --- | --- | | `query` | string, required | The search text | | `location` | string, up to 500 characters | The location to search from | | `gl` | string, up to 2 characters | Country code for the search | | `hl` | string, up to 2 characters | Interface language | | `google_domain` | string, up to 50 characters | Which Google domain to use | | `safe` | `active` or `off` | Safe search | | `tbm` | `isch`, `vid`, `nws`, `lcl`, `shop`, `pts` | Search vertical: images, video, news, local, shopping, patents | | `device` | `desktop`, `tablet`, `mobile` | The device type to search as | | `start`, `page`, `amount` | integer | Paging controls | | `include_thumbnails` | `0`, `1`, `true`, `false` | Whether to include thumbnails | The full list also has `uule`, `cr`, `lr`, `tbs`, `as_qdr`, `kgmid`, `filter`, `nfpr`, `udm` and several other Google-specific parameters. The [Search endpoint page](https://perceptlayer.com/apis/google-search/search) lists every one with its limits. If you're paging through results, the [pagination guide](https://perceptlayer.com/blog/paginate-web-data-api-python) shows a safe loop pattern. ## What are the other six Google Search endpoints for? The Google Search API has 7 endpoints, and each costs 1 credit per call. Pick by the job: the standard and advanced search endpoints return the results page, one endpoint returns the AI Overview, another returns AI Mode answers, one returns place details, and two lighter endpoints cover search and autocomplete. | Endpoint | Use it for | Required parameter | | --- | --- | --- | | [`/v1/google-search/search`](https://perceptlayer.com/apis/google-search/search) | Standard search results | `query` | | [`/v1/google-search/search-advanced`](https://perceptlayer.com/apis/google-search/search-advanced) | Search with the same parameter set as `search` | `query` | | [`/v1/google-search/search-light`](https://perceptlayer.com/apis/google-search/search-light) | Lighter search with `num`, `dateRestrict`, `sort` and `rights` | `query` | | [`/v1/google-search/search-light-autocomplete`](https://perceptlayer.com/apis/google-search/search-light-autocomplete) | Autocomplete suggestions, with `hl` and `limit` | `query` | | [`/v1/google-search/search-ai-overview`](https://perceptlayer.com/apis/google-search/search-ai-overview) | The AI Overview for a query | `query` | | [`/v1/google-search/google-ai-mode-search`](https://perceptlayer.com/apis/google-search/google-ai-mode-search) | Google AI Mode search, with `follow_up_token` for follow-ups | `q` | | [`/v1/google-search/search-advanced-place`](https://perceptlayer.com/apis/google-search/search-advanced-place) | Place details, via `detail_url` or `svid` | none | Two details trip people up. AI Mode uses `q`, not `query`. And `search-advanced-place` has no required parameter; you pass a `detail_url` or `svid` instead. If you're migrating from Custom Search, look at `search-light` first. Its parameters ( `num`, `start`, `dateRestrict`, `sort`, `rights`, `cr`, `lr`, `safe`, `filter`) use names that will look familiar. We haven't recorded a response for it, so check the output in the playground before you map fields. Treat it as a candidate, not a drop-in swap. ## How much does a call cost compared with Custom Search? A successful call costs 1 credit, so 1,000 calls cost 1,000 credits. Credits come in prepaid packs from 10,000 credits (Starter) up to 5,000,000 (Volume), and the [pricing page](https://perceptlayer.com/pricing) shows what each pack costs. Google's Custom Search charges [$5 per 1,000 queries](https://developers.google.com/custom-search/v1/overview) after 100 free queries a day, capped at 10,000 queries a day. | Option | Cost of 1,000 calls | | --- | --- | | Custom Search JSON API (closed to new customers) | $5 per 1,000 queries | | Google Search API here | 1,000 calls × 1 credit = 1,000 credits | The arithmetic for 10,000 queries: 10,000 calls × 1 credit = 10,000 credits, which equals the Starter pack's 10,000. The free tier's 1,000 credits a month cover 1,000 of those calls. Custom Search at $5 per 1,000 would be $50 for the same volume, ignoring its free daily queries. Failed calls cost nothing and return `X-Credits-Used: 0`. Successful responses carry `X-Credits-Used` and `X-Credits-Remaining`, so you can track the balance in code. Purchased credits last 12 months, and there's no subscription. The [credits docs](https://docs.perceptlayer.com/credits) explain how calls are counted. One trade-off to be plain about: Custom Search is Google's own service. If you already have access and it fits, staying until the January 1, 2027 deadline is reasonable. For anything new, it's no longer an option. ## What happens when a call fails? Errors return an HTTP status and a JSON body shaped like `{"error": {"code", "message", "request_id"}}`. Common codes are `invalid_api_key` (401), `insufficient_credits` (402), `invalid_parameters` (422), `rate_limited` (429) and `temporarily_unavailable` (503). The [errors docs](https://docs.perceptlayer.com/errors) list them all. Rate-limited and temporarily unavailable responses include a `Retry-After` header with the seconds to wait. There's no idempotency key, so a request that timed out on your side may have succeeded and been billed. The guide to [retrying without paying twice](https://perceptlayer.com/blog/retry-web-api-calls-without-paying-twice) covers how to handle that, and the [rate limit docs](https://docs.perceptlayer.com/rate-limits) have the rest. If you're feeding results to an agent, the same key works over MCP. See [Claude MCP web search](https://perceptlayer.com/blog/claude-agent-live-search-mcp) and the [MCP docs](https://docs.perceptlayer.com/ai-agents). Next step: [get a free API key](https://perceptlayer.com/signup), then run the Berlin request above and compare `organic_results` with what you get today. ## APIs in this post - [Google Search **1 credit per call** · 7 endpoints](https://perceptlayer.com/apis/google-search) ## Frequently asked questions ### Is the Google Custom Search JSON API still available? Only to existing customers. Google's documentation says the API is closed to new customers and that existing customers have until January 1, 2027 to move to an alternative. Google lists Vertex AI Search for searching up to 50 domains. For general web results as JSON, you need another source. ### How much does a Google search API call cost here? Each successful call to a Google Search endpoint costs 1 credit. That works out to 1,000 credits for 1,000 calls. The free tier gives 1,000 credits every month after email verification, with no credit card required, and the [pricing page](https://perceptlayer.com/pricing) shows what credits cost. ### Can I get AI Overviews and autocomplete as JSON? Yes. `GET /v1/google-search/search-ai-overview` takes a `query` and returns the AI Overview, and `GET /v1/google-search/search-light-autocomplete` returns autocomplete suggestions. Both cost 1 credit. We haven't recorded responses for them, so run each in the playground on the API page to see the fields. ### Am I billed when a request fails? No. Failed calls cost nothing and return `X-Credits-Used: 0`. The one exception to watch is a client timeout: with no idempotency key, a request whose reply you never received may have succeeded and been billed. Check `X-Credits-Remaining` on your next call. ### What if a call returns restricted\_endpoint? Restricted endpoints cover social, personal and SEO data. They work after you accept the restricted-endpoint terms in the dashboard, and until then they return `restricted_endpoint` (403). If you see that code, accept the terms and retry the same call. google search serp search api json custom search ## More from the blog 1. [API guides](https://perceptlayer.com/blog/category/api-guides) 20 Aug 2026 Perceptlayer 6 min read ## [DuckDuckGo Search API: Web Results as JSON](https://perceptlayer.com/blog/duckduckgo-search-api-json) DuckDuckGo's Instant Answer API returns topic summaries, not ranked links. GET /v1/duckduckgo/search returns organic results and paging at 1 credit per query. 2. [API guides](https://perceptlayer.com/blog/category/api-guides) 5 Aug 2026 Perceptlayer 8 min read ## [Bing Search API Alternative: Web Results as JSON](https://perceptlayer.com/blog/bing-search-api-alternative-json) Replace Microsoft's retired Bing Search API with three search endpoints at 1 credit per call. Parameters compared, real responses, and where results differ. 3. [API guides](https://perceptlayer.com/blog/category/api-guides) 16 Jul 2026 Perceptlayer 7 min read ## [Google AI Overview API: Get AI Overviews as JSON](https://perceptlayer.com/blog/google-ai-overview-api) Google has no AI Overview API. GET /v1/google-search/search-ai-overview takes a query, hl and gl, costs 1 credit, and suits daily keyword tracking.