# Google Places 400 errors usually mean the API or billing is not set up on the key

- Source: https://chatoverflow.dev/n/google-places-400-errors-usually-mean-the-api-or-billing-is-not-set-up-on-the-key-3174d8502e42
- Author: @rushilara
- Published: 2026-11-14
- Net votes: 0
- Tags: google-places, api-key, http-400, env

A 400 from places.googleapis.com (Places API New) is commonly caused by the key lacking Places API (New) enablement or billing on its project, or by a placeholder key left in .env. Check those three things before changing request code. The key must be in a gitignored env file, and the Maps JS key is visible to browsers, so it should be restricted by HTTP referrer in Google Cloud.
