# Search Box (Geographic places) fails due to reliance on deprecated Google Places endpoint **URL:** \ **Category:** Need help\ **Created:** [August 26, 2025, 8:26pm UTC](https://forum.bubble.io/t/search-box-geographic-places-fails-due-to-reliance-on-deprecated-google-places-endpoint/379556 "2025-08-26T20:26:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![enzo1](https://avatars.discourse-cdn.com/v4/letter/e/b487fb/32.png) [@enzo1](https://forum.bubble.io/u/enzo1)\ **Post date:** [August 26, 2025, 8:26pm UTC](https://forum.bubble.io/t/search-box-geographic-places-fails-due-to-reliance-on-deprecated-google-places-endpoint/379556/1 "2025-08-26T20:26:45Z")
**What you expected to happen** The **Search Box** element set to **Geographic places** should use the current Google Places/Maps APIs, display autocomplete suggestions, and validate addresses when typing. **What actually happened** The element makes requests to a **deprecated Google Places endpoint** , which now returns errors. As a result: - No autocomplete suggestions appear. - Addresses are not validated. - The entire Search Box flow is unusable. **Steps to reproduce the issue** 1. Add a new Search Box element in Bubble. 2. Configure it with type **Geographic places**. 3. Enable and connect API keys under Settings \> API (Maps JavaScript, Places, Geocoding, Geolocation). 4. Load the page and type any address. **Observed result:** No suggestions are shown. **Console output:** Requests to a deprecated Google Places endpoint fail with an error. HEEEEEEEEEEEELPPPPPP!!! ---
**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\ **Post date:** [November 4, 2025, 8:27pm UTC](https://forum.bubble.io/t/search-box-geographic-places-fails-due-to-reliance-on-deprecated-google-places-endpoint/379556/2 "2025-11-04T20:27:03Z")
Closed on November 4, 2025, 8:27pm UTC This topic was automatically closed after 70 days. New replies are no longer allowed.