Bubble actions that call Google Places and Geocoding APIs

Hi all,

Does someone have a simple list of all the bubble actions, data sources or expressions that call Google Geocoding and Places APIs?

This is mainly to track down areas where API calls could be conserved.

Thanks for any help.

Regards,
Mihira

i don’t have a complete list, but (for example) whenever you reference a geographic location’s Timezone, that’s a live call to Google’s API. Similarly, I’m pretty sure that referencing a geo location’s “formatted address” does the same.

Having a repeating group that displays these things is a good way to rack up API calls. So, when you acquire a geo location, you should cache and store derivative values that you will reference frequently later.

(This is not documented.)

Old thread on this:

(Note that the bug I refer to in the end of the thread is long solved — bubble was making the calls incorrectly [sans key], but it took quite a while for that to get fixed. When working with Bubble, file bug reports early and often.)

1 Like

Thanks for the advice. Yes formatted addresses are a sneaky one that needs to be stored when acquired.

1 Like