Google Custom Search API Key

The Google Custom Search JSON API lets you build websites and applications that retrieve and display search results from Google Custom Search programmatically. With this API, you can use RESTful requests to get web search or image search results in JSON format. To make API calls, you need a Google Custom Search API key — a unique credential that identifies your application to Google’s servers. In this guide, we’ll walk through how to get your Google search API key, where to find it after creation, how to troubleshoot common errors, and what best practices to follow.

How to Get a Google Custom Search API Key (Step-by-Step)

If you are an existing Google Custom Search JSON API user, follow these steps to create or retrieve your API key:

Step 1: Go to Google Cloud Console

Navigate to console.cloud.google.com and sign in with your Google account. This is where all Google API credentials are managed.

Step 2: Create or Select a Project

Click the project dropdown at the top of the page. You can either select an existing project or click New Project to create one. Give your project a descriptive name (e.g., “My Site Search”) and click Create.

Step 3: Enable the Custom Search JSON API

1. From the left sidebar, go to APIs & Services → Library.
2. Search for “Custom Search JSON API” in the search bar.
3. Click on the API result and then click the Enable button.

You must enable the API before you can create credentials for it.

Step 4: Create Your API Key Credentials

1. Go to APIs & Services → Credentials.
2. Click + CREATE CREDENTIALS at the top of the page.
3. Select API key from the dropdown.
4. Your new Google search API key will be generated and displayed in a dialog box. Copy it immediately.

Step 5: Restrict Your API Key (Critical for Security)

Never leave your API key unrestricted. Click Restrict Key in the dialog (or edit the key later) and apply these restrictions:

• API restrictions: Select “Restrict key” and choose only Custom Search JSON API from the list.
• Application restrictions: Restrict by HTTP referrers (websites) or IP addresses depending on your use case.

This prevents unauthorized usage and unexpected charges on your account.

Where to Find Your Google Custom Search Engine API Key

If you’ve already created a key and need to find it again:

1. Open Google Cloud Console → Credentials.
2. Select the correct project from the dropdown at the top.
3. Your API keys are listed under the API Keys section. Click the key name to view or copy it.

You also need your Custom Search Engine ID (the cx parameter). Find it in the Programmable Search Engine Control Panel under Setup → Basics → Details. After you have both, your API calls will look like this:

https://www.googleapis.com/customsearch/v1?key=YOUR_API_KEY&cx=YOUR_CX&q=search+term

Common Errors and How to Fix Them

Error	Cause	Fix
403 Forbidden	Invalid API key, API not enabled, or key restrictions blocking the request	Verify the key in Cloud Console, ensure Custom Search JSON API is enabled, and check key restrictions
429 Too Many Requests	Exceeded daily quota (free tier: 100 queries/day)	Wait for quota reset, enable billing for higher limits, or upgrade your plan
400 Bad Request	Missing or malformed cx or key parameter	Double-check both parameters in your API request URL

How to Regenerate Your API Key

If your key is compromised or not working, regenerate it:

1. Go to APIs & Services → Credentials in Google Cloud Console.
2. Click the three-dot menu next to your API key.
3. Select Regenerate key. The old key will stop working immediately.
4. Update your application with the new key.

API Key Best Practices

Follow these practices to keep your Google Custom Search API key secure:

• Restrict the key to Custom Search API only — don’t leave it open to all Google APIs.
• Never expose the key in client-side code — JavaScript files, HTML source, or public repositories can be scraped by bots.
• Use environment variables — store keys in .env files or your server’s environment configuration rather than hardcoding them.
• Rotate keys periodically — regenerate keys every few months as a security measure.
• Monitor usage — check the Cloud Console dashboard regularly for unexpected spikes in API calls.

Alternatives to Google Custom Search JSON API

Since the Google Custom Search JSON API is closed to new customers as of 2025, you’ll need an alternative if you’re setting up site search for the first time. Even existing users should plan their migration before the January 2027 deadline. ExpertRec is a drop-in replacement that provides site search without the complexity of managing API keys, quotas, or custom code. Key advantages include:

• No API key management — get started with a simple code snippet instead of configuring credentials, projects, and billing.
• 5-minute setup — add search to your website by pasting one line of code.
• Content search plans from $49/mo — predictable pricing without per-query charges.
• Built-in analytics — see what visitors are searching for on your site.

Try ExpertRec Search — No API Key Required

For a deeper dive into the Custom Search JSON API and its capabilities, read our comprehensive guide: Google Custom Search JSON API Simplified.