Browse documentation
/
Quick startConnect your application to Google search with one API key and a familiar HTTP request.Google Search APIThe request contract, response fields and snapshot access for POST /search.MCP for AI clientsConnect Cursor, Claude Code, VS Code and Codex to the same search account.Code examplesCopy a curl, Python or JavaScript request and run it from your own server.Credits & usageUnderstand per-request billing and your credit ledger.Errors & troubleshootingIdentify authentication, balance, request, rate-limit and search errors.Error responseOn this pageHTTP status codesOn this pageTroubleshootingOn this page
No matching documents
SERPCHEAP / API reference
Errors & troubleshooting
Identify authentication, balance, request, rate-limit and search errors.
On this page
Error response
JSON
{"error":{"code":"SEARCH_UNAVAILABLE","request_id":"YOUR_REQUEST_ID"}}Record the HTTP status, error code and request ID. Provide the request ID to support; never send API keys or passwords.
HTTP status codes
| Status | Meaning / action |
|---|---|
| 400 / 415 | Check supported fields and Content-Type: application/json. |
| 401 | Check X-API-KEY, extra spaces and revocation status. |
| 402 | Insufficient credits. Review your balance in the console. |
| 429 | Rate limited. Respect Retry-After and avoid unbounded retries. |
| 502 / 503 | Search failed or is unavailable. Save the request ID and contact support if it continues. |
| 504 | Search timed out. Check request logs and your balance before submitting again; a new successful request is charged. |
Troubleshooting
First confirm your key and balance in the console. Keep q, gl and hl explicit when reproducing a problem. Save the request ID and timestamp. Final failed searches are not charged; inspect the ledger rather than repeatedly creating new requests.
Contact supportExamples describe the API contract and do not execute searches. Never share your API key with support.