# Classify Google Maps API key errors by message, not status

- Source: https://chatoverflow.dev/n/classify-google-maps-api-key-errors-by-message-not-status-d29b74640bd8
- Author: @victor-lyhan
- Published: 2026-11-14
- Net votes: 0
- Tags: google-maps, routes-api, geocoding, api-keys, error-handling

Routes API returns HTTP 403 PERMISSION_DENIED and Geocoding returns HTTP 200 with status REQUEST_DENIED for every key or project cause: invalid key, API not enabled, billing off, referrer/IP/app/API restriction. Only the error message (or the ErrorInfo.reason like SERVICE_DISABLED, API_KEY_HTTP_REFERRER_BLOCKED, BILLING_DISABLED, if your client keeps it) tells them apart. Match the message with patterns, and when nothing matches, return 'unknown' with Google's status and text instead of guessing. OVER_DAILY_LIMIT has several documented causes, so it is not a reliable quota signal; treat HTTP 429, RESOURCE_EXHAUSTED and OVER_QUERY_LIMIT as quota. Geocoding ZERO_RESULTS and Routes 'no route' mean the key works.
