Google Custom Search setup: three pieces and what each error code means

Not specified by the original author.

TL;DR

Run the checklist in order when search calls fail.

The error

three pieces and what each error code means

Fix

1. Run the checklist in order when search calls fail. Expected: you can confirm this matches your situation.

2. Re-run the original operation and confirm the error is gone. Expected: no error, normal output.

When to use

• You hit this exact error with Google Custom Search setup.
• The symptom matches: three pieces and what each error code means.

When NOT to use

• A different error message from Google Custom Search setup; the cause here is specific to this error.
• Unrelated Google Custom Search setup issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Google Custom Search setup.

Variant phrasings

three pieces and what each error code means

Why it happens

Web: a Google API integration guide documents the setup checklist and the error table that trips first-time integrators. You need three things: a Google Cloud project, the Custom Search API enabled on it, and a Programmable Search Engine whose ID you pass as cx. The guide maps the common failures: 400 is a bad request, check query and key; 403 means the API is not enabled for the key or billing and quota restrictions apply; 429 means rate limit or quota exceeded, wait for the reset or enable billing; and an invalid-key message means re-entering the key. Source: https://github.com/purelogiccode/findromcover/blob/HEAD/docs/user-guide/google-api.md

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Web: a Google API integration guide documents the setup checklist and the error table that trips first-time integrators. You need three things: a Google Cloud project, the Custom Search API enabled on it, and a Programmable Search Engine whose ID you pass as cx. The guide maps the common failures: 400 is a bad request, check query and key; 403 means the API is not enabled for the key or billing and quota restrictions apply; 429 means rate limit or quota exceeded, wait for the reset or enable billing; and an invalid-key message means re-entering the key. Source: https://github.com/purelogiccode/findromcover/blob/HEAD/docs/user-guide/google-api.md Resolved: run the checklist in order when search calls fail. One, confirm the Custom Search API is enabled in your Cloud project, a 403 almost always means this step was skipped. Two, confirm billing is enabled if you need more than 100 queries a day, otherwise the 101st call 429s. Three, confirm the cx value is your Programmable Search Engine ID and the key belongs to the same project. Read the status code, dont guess: 400 is your request, 403 is enablement or billing, 429 is quota. And keep the key server-side or behind your own API route; a key embedded in a client app gets scraped and burns your quota. Source: https://github.com/purelogiccode/findromcover/blob/HEAD/docs/user-guide/google-api.md