Forum Documentation Showcase Pricing Learn more

🎡 Algolia Places - New Plugin from Zeroqode


Algolia Places provides a fast, distributed and easy way to use address search autocomplete JavaScript library on your website. It has been designed to improve the user experience of your forms.

It harnesses OpenStreetMap’s impressive open source database of worldwide places.

For details, screenshots and demos please visit the plugin page: at

Levon Terteryan

Founder @ Zeroqode


Bubble Templates

Bubble Plugins

Bubble Courses

Convert Web to iOS & Android

No-code Development Services


Hi, I am setting this plugin now and have got a question.
While restricting the type of search results, is it possible to select 2 specific types such as address and city, instead of choosing only one type?
If possible, how can I do that?

Hi, unfortunately, it is possible to have only one type selected or all as by default.


How do you restrict the result so that it must come from the auto complete? I.e. if a user leaves in an incomplete address or an address Algolia does not recognize then the input is invalid.


Hi @Dimitrii,

Thanks for reaching out. In case you want to restrict the results from auto complete, you can add a button to your search and implement logic to display data only when you press the search button.

Best regards,
Zeroqode Team

1 Like

@zeroqode @levon

After purchase of this plugin are there any monthly fees or any other costs involved in using the plugin? Specifically wondering if I need to subscribe to algolia or OpenStreetMap’s?

Hi @boston85719
yes, you’d need to have an algolia account
you can see the pricing details here:

Thanks for the link.

I am confused about which choice would be better for my app based on potential costs associated.

  1. Zeroqode fastest google places autocomplete
  2. Zeroqode Algolia Places

My goal is to allow users to enter their address for the purpose of providing search results close to their location. These search results are coming from my D.B. of saved retailers and job listings. The main purpose of the plugin is only really to fetch the city, state and country once the user has inputted and selected their address.

Looking at Algolia pricing, it seems that once my app has exceeded 100,000 requests for places there is a charge of $0.40 per 1,000 requests.

My assumption is that a request is simply a user inputting their address into the search input. So for example, a user navigates to the search page, inputs a single address into the input and selects, that alone is a single request. So if the same user changes their address using the search input, that would be a second request and so this single user has made two requests.

Then looking at google pricing, which is so much more confusing than Algolia.

I have a really hard time understanding which of these two pricing structures would be used when I have the Zeroqode Fastest Google Places Autocomplete plugin used for the purposes of allowing a user to enter their address and select it from the list of choices and subsequently extracting that address city, state and country.

Could you shed some light onto the google pricing that is associated with the zeroqode fastest google places autocomplete plugin and if my assumption of the Algolia pricing is correct?

I really don’t know which google pricing is used, the SKU: Autocomplete - Per Request or the SKU: Basic Data.

Hello @boston85719, thank you for reaching out!

Yes, your assumption regarding Algolia pricing is correct. The pricing model for Google Places Autocomplete is SKU: Autocomplete - Per Request.

Best Regards,
Zeroqode Team

Thanks for the confirmation. Seems like Algolia is the way to go then.

Comparing the two looks like Algolia gives for free what Google charges $283 a month for being the first 100,000 requests a month.

Going to a higher range of 500,000 requests a month Algolia is $160 compared to Google at $1,135.

I guess the real trick to saving money on searches is grabbing the users location and having it as the default value in the input and hope they don’t even need the autocomplete.