Algolia Search V2.0 is a Bubble plugin that enables ultra-fast, scalable, and flexible search functionality powered by Algolia. The plugin allows you to search, filter, paginate, and retrieve complete objects from Algolia indexes directly inside Bubble workflows and elements.
Version 2.0 introduces improved performance, full object return support, advanced faceting, filtering, and pagination features, making it suitable for both small datasets and large-scale applications.
Prerequisites
For using the plugin you'll need to get the API credentials from Algolia. Create your development account at: https://www.algolia.com/developers/
How to setup
This section guides you step by step through the process of setting up the Algolia Search V2.0 plugin in Bubble.
You will learn how to configure your Algolia account, obtain the correct API keys, and connect the plugin so you can start using search, filtering, and data management features.
Follow the steps below to ensure a correct and secure plugin setup.
Step 1 – Install the Plugin
Go to the Plugin Tab
Open your Bubble Editor.
Navigate to the Plugins tab on the left panel.
Add Plugins
Once in the Plugins tab, click the Add Plugins button.
Search for the Plugin
Use the search bar to type Algolia.
Locate the plugin in the search results.
Install/Buy
If the plugin is free, click Install to add it to your application.
For a paid plugin, click Buy and follow the purchase instructions.
Payment Information (For Paid Plugins)
If the plugin is a paid one, fill in your payment details and make payment.
Charges will be added to your Bubble billing account.
Remember, if you unsubscribe from the plugin shortly after installation, charges will be prorated based on the days used.
Plugin Installed
Once installed, the plugin will appear under the Installed Plugins list in your Bubble Editor.
Step 2 – Algolia Dashboard Getting the Correct API Keys
To use the Algolia plugin, you must configure your account in the Algolia Dashboard and obtain the correct API keys.
Here you will find multiple keys. The most important ones are:
Application ID – your Algolia application identifier.
Search-Only API Key – used for search operations (safe for client-side usage).
Admin API Key – used for administrative actions (update, delete, index settings).
Security recommendations
Use the Search-Only API Key for search operations.
Use the Admin API Key only for actions such as:
Set Algolia Settings
Update Objects
Delete Objects
Add Objects
☝
Never expose the Admin API Key in public or client-side environments
Step 3 – Set the API keys in Bubble
Open your Bubble Editor
Go to Plugins → Algolia Search V2.0
Paste the keys as follows:
Application ID → Application ID field
Search-Only API Key → Search API Key field
Admin API Key → Admin API Key field
☝
Setting API keys alone is not enough.
You must also configure searchable and facetable attributes in the Algolia Dashboard for the plugin to work correctly.
Step 4 – Required Index Configuration
After setting the API keys, you must also configure your Algolia index settings
in the Algolia Dashboard. Without these settings, search, filtering, and faceting may not work as expected.
1️⃣ Configure searchable attributes
Algolia searches only within attributes explicitly marked as searchable.
Steps:
Open Algolia Dashboard
Select your index
Go to Configuration
Open Searchable attributes
Add the fields you want to search in (for example: title, description)
Save the settings
2️⃣ Configure attributes for faceting (required for filters)
To use filters or facet-related actions, attributes must be declared as facetable.
Steps:
Open Facets
Add the required attributes using:
plain text
searchable(attribute_name)
Example:
plain text
searchable(category)searchable(tag)
Save the settings
ℹ️ This step is mandatory for actions like Search for Facet Values.
Step 5 – Add the Plugin Element to Your Page
Open the Design tab in your Bubble editor.
Search for the Algolia Simple Search element in the Elements panel.
Step 6 – Basic element configuration
These settings are required for the element to work.
Only as a search - If enabled, the element works only as a search engine and does not render visual results.
Index Name - Set the exact name of your Algolia index
Query - Bind the Query to a Bubble Input: “Input Search's value”
Fields to Retrieve - Add a comma-separated list of fields that exist in your Algolia objects:
javascript
title, description, icon, objectID
⚠️ Only fields listed here will be available in the results.
Tutorial
Plugin Element - Algolia Simple Search
A visual element that performs real-time Algolia searches and exposes results, facets, and pagination data to Bubble.
Fields
Field name
Description
Type
Only as a search
If enabled, the element works only as a search engine and does not render visual results
Yes / No
Index Name
Name of the Algolia index where the search is performed
Text
Query
Search input value (usually linked to an Input element)
Text
Type of Content
Defines the type of content returned by the search
Algolia Result
Fields to Retrieve
Comma-separated list of object attributes returned from Algolia
Text
Hits Per Page
Number of results returned per page
Number
Page
Page number used for pagination (starts from 0)
Number
Proximity
Controls how close the search terms must be to each other
Number
Filters
Algolia filter expression (e.g. status:active AND tag:plugin)
Text
Restrict Searchable Attributes
Limits the search to specific attributes only
Text
Filter Unique Items
Removes duplicate results based on a unique attribute
Text
Around Lat-Lng
Latitude and longitude for geo-based search (lat,lng)
Text
Around Radius
Radius (in meters) used for geo-search
Number
Timeout
Maximum time allowed for the search execution (ms). 0 means no limit
Number
Search begins when typing is finished
Executes search only after the user stops typing
Yes / No
Shuffle Hits
Randomizes the order of returned search results
Yes / No
Paginate all pages
Retrieves and merges results from all available pages
Yes / No
Element Actions
Search for Facet Values.
Searches and returns available values for a specific facet attribute from an Algolia index, based on the provided query.
This action is typically used to build autocomplete dropdowns, facet filters, or dynamic filtering UI.
Field name
Description
Type
Element
The AlgoliaSimpleSearch element used to perform the facet search
AlgoliaSimpleSearch
Facet Name
Name of the facet attribute configured in Algolia
Text
Facet Query
Text used to filter facet values
Text
To use this action, it is necessary to make some settings in the Algolia dashboard.
Select "configuration”
Search under the option "Facets”
Here you set the field by which you search in "searchable”, and press the button “save setting”
Action setting:
Facet Name - Attribute name. For this to work, you must declare the attribute with attributesForFaceting using the searchable() modifier.
Facet Query - The search query used to search the facet attribute.
Filters - Here you can additionally add a filter. To create a filter correctly, please follow our documentation in the "Filtering" section.
Max Facet Hits - Maximum number of facet hits to return during a search for facet values. Data of this action will be stored in the following states:
How many values of this type were found - List with the number of times the value is present in the dataset.
Highlighted Values - List Highlighted values
List Of Values - List with "Facet value”.
Algolia Refresh
Algolia Refresh refers to the process of updating an Algolia index to ensure it contains the most recent and accurate data.
This operation is typically used after data changes (create, update, or delete) to make sure search results reflect the latest state of the dataset.
Refreshing an index may include:
Re-indexing updated records
Syncing newly added data
Removing outdated or deleted entries
Use Algolia Refresh whenever your application data changes and search results must stay in sync with your database.
Recent Searches
Returns a list of the most recent search queries performed using the selected
AlgoliaSimpleSearch element. This action is useful for building features like
recent searches history, search suggestions, or quick re-search buttons.
Field name
Description
Type
Element
The AlgoliaSimpleSearch element used to retrieve recent searches
AlgoliaSimpleSearch
Query
The search value to be stored or matched in recent searches
Text
Element States
Name
Description
Type
Result
Contains the full Algolia search response, including all returned records and metadata, based on the fields defined in Fields to Retrieve
List of Algolia Result
Suggestions
Stores a list of keywords previously searched by the user
List of Text
Recent Searches
Contains recent search queries returned by the Recent Searches action. If the Query field is empty, all recent searches are returned
List of Text
Facet Values
Returns the list of facet values from the Search for Facet Values action
List of Text
Highlighted Values
Highlighted facet or search values returned by Algolia
List of Text
Facet Values Count
Indicates how many times each facet value appears in the dataset
List of Numbers
How work Algolia Result state
The Algolia Result state is a complex object that contains all the information related to a search query in one place.
It stores data as lists grouped by user-defined fields, based on the fields specified in Fields to Retrieve from the element settings.
For example, if you select the following fields:
Name
Genre
Estimated Sales
First Post
Then, in the Algolia Result state, you will have access to:
Field 1 → list of Name values
Field 2 → list of Genre values
Field 3 → list of Estimated Sales values
Field 4 → list of First Post values
Each of these fields contains a list of values returned from your Algolia objects.
Indexing logic
All field lists use the same index order:
Field 1 : item #1 → Name of the first Algolia object
Field 2 : item #1 → Genre of the same object
Field 1 : item #2 → Name of the second Algolia object
and so on…
Property
Description
Type
query
The search query that was requested
Text
queryID
Unique identifier of the search query
Text
params
Parameters used for the search request
Text
hitsPerPage
Number of results returned per page
Number
nbHits
Total number of matching results
Number
nbPages
Total number of available pages
Number
page
Currently requested page
Number
field 1
List of values for the first field defined in Fields to Retrieve
List of Text
field 2
List of values for the second field defined in Fields to Retrieve
List of Text
…
Additional fields in the same order
—
field 20
List of values for the twentieth field defined in Fields to Retrieve
List of Text
Element Events
Title
Description
Algolia is Loading
Algolia loading refers to the state in which the Algolia search engine is in the process of retrieving, processing, or displaying data from the index.
Plugin Actions Server-Side
☝
Set Algolia settings
Index settings are built directly into your index at indexing time, and they impact every search. Only specified settings are overridden; unspecified settings are left unchanged. Specifying null for a setting resets it to its default value.
Set Algolia settings.
The Set Algolia Settings action allows you to configure how an Algolia index behaves.
Using this action, you can define search behavior such as ranking, sorting, faceting, and other index-level settings directly from Bubble.
This action is typically used during:
initial index setup
reconfiguration after schema changes
advanced search optimization
Title
Description
Type
Index Alglia
An index is a collection of data optimized for fast and efficient search
Text
Attributes
Searchable Attributes
The complete list of attributes used for searching.
Text (optional)
Attributes For Faceting
The complete list of attributes that will be used for faceting
Text (optional)
Attributes To Retrieve
This parameter controls which attributes to retrieve and which not to retrieve.
Text (optional)
Ranking
Ranking
Controls how Algolia should sort your results.
Text (optional)
Custom Ranking
Each string must conform to the syntax asc(attributeName)ordesc({attributeName}) and specifies a (respectively) increasing or decreasing sort on an attribute. All sorts are applied in sequence by the tie-breaking algorithm in the order they are specified.
Text (optional)
Relevancy Strictness
Controls the relevancy threshold below which less relevant results aren’t included in the results.
Number (optional)
Replicas
Creates replicas, exact copies of an index.
Text (optional)
Faceting
Max Values Per Facet
Maximum number of facet values to return for each facet during a regular search. For performance reasons, the API enforces a hard limit of 1000 on maxValuesPerFacet. Any value above that limit will be interpreted as 1000.
Number (optional)
Sort Facet Values By
Controls how facet values are fetched. Available options: count, alpha
Dropdown (optional)
Typos
Min Word Size for1 Typo
Minimum number of characters a word in the query string must contain to accept matches with 1 typo.
Number (optional)
Typo Tolerance
Controls whether typo tolerance is enabled and how it is applied. Available options: true, false, min, strict
Dropdown (optional)
Disable Typo Tolerance On Attributes
List of attributes on which you want to disable typo tolerance.
Text (optional)
Update Objects
In Algolia, the Update Objects action is used to modify or replace existing records in an index without deleting other fields of the object.
This action updates only the fields provided in the request. Any fields not included remain unchanged.
Title
Description
Type
Index
Name of the Algolia index where the objects will be updated
Text
Objects
List of records to update, formatted as JSON
Text
Return Values:
Title
Description
Type
ObjectIDs
The list of IDs of the objects update in the index.
Text
Delete Objects
Set the list of ids in the "List of objects id" field, separating them with ",”.
Title
Description
Type
Index
An index is a collection of data optimized for fast and efficient search
Text
Objects
List of objectIDs to delete.
Text
Return Values:
Title
Description
Type
ObjectIDs
The list of IDs of the objects delete from the index.
Text
Add Objects
Add new objects to an index or replace existing objects with an updated set of attributes.
The save method is used to redefine the entire set of an object’s attributes (except its objectID). In other words, it fully replaces an existing object.
With Save Objects, you define an object’s full set of attributes. Attributes not specified will no longer exist. For example, if an existing object contains the author attribute, but you don’t define it in your update call, it removes the author attribute from that object.
In contrast, when using Partial Update Objects, you can single out one or more attributes and create or update their content. If you don’t define an existing attribute in your update call, it doesn’t impact it.
Title
Description
Type
Index
An index is a collection of data optimized for fast and efficient search
Text
Objects
A list of records to save.
Text
Return Values:
Title
Description
Type
ObjectIDs
The list of IDs of the new objects added to the index.
Text
Workflow example
Searching Data in Algolia
These settings are required for the element to work.
Index Name - Set the exact name of your Algolia index
Query - Bind the Query to a Bubble Input: “Input Search's value”
Fields to Retrieve - Add a comma-separated list of fields that exist in your Algolia objects:
javascript
title, description, icon, objectID
⚠️ Only fields listed here will be available in the results.
📊 How to display fields inside the Repeating Group
UI Element
Expression
Text (Name)
Current cell's text(from field 1)
Text (Genre)
AlgoliaSimpleSearch's Result's field 2:item Current cell's index
Text (Estimated Sales)
AlgoliaSimpleSearch's Result's field 3:item Current cell's index
Text (First Post)
AlgoliaSimpleSearch's Result's field 4:item Current cell's index
Adding Indexing Data in Algolia
Event: Button clicked
Action: Add Objects
Index = Name of the Algolia index where the objects will be added
Objects = The Objects field must contain a JSON array of objects.
Each object represents a record that will be indexed in Algolia.
Record becomes searchable immediately
Update Indexing Data in Algolia
Updating indexing data in Algolia allows you to modify existing records without re-adding or re-indexing the entire dataset.
This is useful when only certain fields of an object need to be changed, such as status updates, price changes, or content edits.
Event: Button clicked
Action: Update Objects
Index = Name of the Algolia index containing the objects
Objects = JSON array with objects to update (must include objectID)
☝
Important notes
Field names must match exactly the fields used in your Algolia index
Values can be dynamic (for example, Bubble Input values)
This action creates new records and does not update existing ones
To modify existing records, use Update Objects
☝
If you don’t provide an objectID, Algolia will automatically generate one.
Faceted Filtering (Filters)
Faceted filtering allows users to narrow down search results by applying filters based on predefined attributes, such as categories, tags, status, or other structured fields.
This makes search results more relevant and improves the overall user experience
Filter By Text
For example, you have a database of books and you want to select all the books with a certain genre.
Algolia’s filters parameter allows you to leverage boolean operators (AND, OR, NOT) and parentheses to combine individual filters, similar to SQL expression syntax.
As an example now we want to find the fantasy genre only in Portugal, we will use the keyword 'AND'.
Now we are creating a filter to receive all the fantasy and adventure books, we will use the OR operator.
Filter By Numeric Value
Algolia allows you to numerically filter results, via comparison or a range. This only works if you’re using numeric values.
Algolia supports <, <=, =, !=, >= and > operators with the same semantics as in virtually all programming languages.
For example, you want to get all books written between 1887 and 1988, in such cases, we will use the operator "TO".
Result:
Filter By Boolean
Algolia allows you to filter results by boolean attributes. Imagine you have an eCommerce website, and you want users to search through available products. If you have a boolean attribute called is_available, you can exclude all records where is_available is false. To do this, you must first declare is_available as an attribute for faceting.
Filter By Date
Dates aren’t only useful for sorting. You can also leverage them to filter search results on a specific date range. Imagine you have a blog, and you want to provide time-based filters. For example, you may want to allow users to filter on recent posts, or only see posts from a certain period.
Before we can filter on a date, we need to add the date as a Unix timestamp. We don’t have to remove or change the date; instead, we can add a date_timestamp attribute with the proper format.
We can also use TO and NOT operators here.
Note that this attribute needs to be a numeric value for Algolia to be able to sort on it.
We put data in Algolia in Unix timestamp.
2. Filter the data by time as follows. The bubble date must also be in unix format.
Algolia filters use a SQL-like syntax, which allows you to use comparison operators.
Filter an Array
What’s an array in the context of filtering? When you start filtering, many of your filter attributes will take only a single value per record.
For example, in a book index, if you filter by type of story (novel, short story), you only need to tag each book with a single value - normally, a book can’t be both a novel and a short story.
On the other hand, other attributes, like genre, can often contain multiple values: the same book can be included in the “crime”, “comedy”, and “historical” genres. The genre attribute, therefore, needs to be an array.
Generally speaking, any attribute that contains a list of values for a single record needs to be set up as an array. A single value attribute takes a string as a value; multiple values require an array, whose syntax changes depending on the programming language used.
Multilingual Search
Since Algolia’s search engine is language-agnostic, it supports all languages and alphabets, including symbol-based languages such as Chinese and Japanese.
Below are represented steps of how to organize your indices to enable multi-language search.
1. Create one index for all languages. Your records should contain text for each language.
2. In the plugin element -> in the "Fileds to Retrieve'' specify the field name exactly as in the records (point 1).
3. In Algolia Dashboard set the searchable attributes for all required languages.
Recently Searched Queries
The Recently Searched Queries feature allows you to store and display the latest search terms entered by users when performing searches with the AlgoliaSimpleSearch element. If the Query field is empty, the action returns all recent searches.
If a Query value is provided, only matching recent searches are returned.
Trigger the action
Use the Recent Searches action in a workflow.
Typical triggers:
When an input is focused
When a button is clicked
When the page is loaded
Display the results
Use the Recent Searches state as a data source
Display the results in a Repeating Group or dropdown
Example workflow (short)
Event: Input Search is focused
Action: Recent Searches (AlgoliaSimpleSearch)
Display results in a Repeating Group
☝
Important notes
Recently searched queries are collected per user session
This feature works only with AlgoliaSimpleSearch
Geo-Search (Location-Based Search)
Geo-Search allows you to filter search results based on the user’s geographical location.
This feature is useful when you want to return only results that are near a specific point, such as stores, events, services, or users.
Geo-search is performed using the AlgoliaSimpleSearch element and Algolia’s built-in location indexing.
Algolia filters results based on:
a latitude and longitude point
a radius around that point
Only records located within the specified radius are returned.
Required data structure (very important)
☝
Without _geoloc, geo-search will not return any results.
To use geo-search, each object indexed in Algolia must include location data in the following format:
json
"_geoloc":{"lat":47.0105,"lng":28.8638}
Required Algolia setup
Open Algolia Dashboard
Select your index
Make sure objects include the _geoloc attribute
Save and re-index data if necessary
No additional faceting configuration is required for geo-search.
Geo-search is configured directly in the AlgoliaSimpleSearch element.
FAQ
Question: What are the key differences between this plugin and the bubble integration on Pro plans?
Response: please find a feature comparison table below:
Algolia Search V 2.0
Algolia integration to Bubble
✅ Works with any plan.
Requires a Professional plan.
✅ No need for manipulations in the app database
Requires object creation in the app database, same as in the Algolia dashboard.
✅ The Algolia data can be displayed not only on search demand but also when loading pages.
Can only be used as a search tool.
✅ The user can change the Algolia index settings from the Bubble app.
Algolia index settings can be changed only in the Algolia dashboard.
✅ It can update, edit, delete, and add items from Algolia.
❌
✅ Has action that preserves recent user searches.
❌
✅ Has an action that searches for facet values.
❌
✅ A search filter can be added.
❌
✅ Has the possibility to trigger the search right after the user stops typing a search key, to reduce the number of requests to the Algolia platform (reducing the overall costs of the service).
❌
Changelogs
Update 09.01.26 - Version 3.82.0
added the processing of empty numbered values to actions 'Add Objects' and 'Update Objects'.
Update 01.12.25 - Version 3.81.0
Bubble Plugin Page Update (Description).
Update 29.10.25 - Version 3.80.0
Bubble Plugin Page Update (Description).
Update 29.10.25 - Version 3.79.0
Bubble Plugin Page Update (Description).
Update 29.10.25 - Version 3.78.0
Bubble Plugin Page Update (Description).
Update 12.09.25 - Version 3.77.0
Bubble Plugin Page Update (Forum).
Update 09.09.25 - Version 3.76.0
New option: Paginate all pages.
Update 02.09.25 - Version 3.75.0
Import the dependent libraries into the memory allocated for the plugin.
Update 09.06.25 - Version 3.74.0
Marketing update (minor change).
Update 03.06.25 - Version 3.73.0
Marketing changes (minor update).
Update 21.03.25 - Version 3.72.0
Added Field Restrict Searchable Attributes
Update 24.10.24 - Version 3.69.0
Minor update (Marketing update).
Update 19.07.24 - Version 3.68.0
Minor update.
Update 16.07.24 - Version 3.67.0
Minor update (Marketing update).
Update 10.06.24 - Version 3.66.0
Minor update.
Update 10.06.24 - Version 3.65.0
Updated demo/service links.
Update 06.06.24 - Version 3.64.0
Minor update.
Update 10.05.24 - Version 3.63.0
QueryID added to result object
⚠️
To avoid errors, after updating the plugin to version 3.29.0, please be sure to check the “Update Object” action setup.
Update 30.04.24 - Version 3.62.0
fixed problem with data update.
Update 08.04.24 - Version 3.61.0
Was added new options "Filtering unique items".
Update 04.04.24 - Version 3.60.0
updated description.
Update 03.04.24 - Version 3.59.0
Was fixed action 'Refresh'.
Update 17.03.24 - Version 3.58.0
Fixed issue with first letter always getting searched.
Update 26.02.24 - Version 3.57.0
was added action delete object in backend.
Update 06.02.24 - Version 3.56.0
Deprecated action "delete object".
Update 24.01.24 - Version 3.55.0
Was added option "Shuffle Hits".
Update 24.01.24 - Version 3.54.0
updated description.
Update 03.01.24 - Version 3.53.0
fixed action Add objects (backend) and migrated plugin to version 4.
Update 27.12.23 - Version 3.52.0
updated description.
Update 26.12.23 - Version 3.51.0
updated description.
Update 19.12.23 - Version 3.50.0
updated description.
Update 13.11.23 - Version 3.49.0
Fixed action Refresh.
Update 19.10.23 - Version 3.48.0
Updated description.
Update 11.10.23 - Version 3.47.0
Update Algolia to V4.
Update 18.09.23 - Version 3.46.0
updated description.
Update 13.09.23 - Version 3.45.0
minor updates.
Update 06.09.23 - Version 3.44.0
Obfuscation.
Update 10.07.23 - Version 3.43.0
updated description.
Update 17.06.23 - Version 3.42.0
Updated the description .
Update 16.06.23 - Version 3.41.0
Updated the description .
Update 26.04.23 - Version 3.40.0
added options Search begins when taping is finished.
Update 13.04.23 - Version 3.39.0
"improve search for to decrease numarul de requests to Algolia".
Update 04.04.23 - Version 3.38.0
added field "Timeout".
Update 15.03.23 - Version 3.37.0
improve plugin with access object with more leve.
Update 27.02.23 - Version 3.36.0
fixed problem parsing with field null.
Update 21.02.23 - Version 3.35.0
updated the description.
Update 03.02.23 - Version 3.34.0
Add objects backend.
Update 03.02.23 - Version 3.33.0
Added action.
Update 02.02.23 - Version 3.32.0
Updated description.
Update 20.01.23 - Version 3.31.0
"Added new action 'Save Objects'".
Update 20.01.23 - Version 3.30.0
Updated description.
Update 28.10.22 - Version 3.29.0
Field updated.
Update 06.10.22 - Version 3.28.0
was added new actions "Search for Facet Values" and "Delete Objects".
Update 19.09.22 - Version 3.27.0
Adjusted common part.
Update 29.08.22 - Version 3.26.0
Updated common part.
Update 11.08.22 - Version 3.25.0
Updated common part.
Update 21.06.22 - Version 3.24.0
added states lost.
Update 12.04.22 - Version 3.23.0
updated API Endpoint.
Update 28.03.22 - Version 3.22.0
Updated name for API call.
Update 16.03.22 - Version 3.21.0
minor fixies.
Update 21.02.22 - Version 3.20.0
Added refresh action.
Update 28.11.21 - Version 3.19.0
Added function (add object, set setting, Get all data).
Update 28.07.21 - Version 3.18.0
Updated description.
Update 14.07.21 - Version 3.17.0
Updated icon.
Update 21.11.20 - Version 3.16.0
Added new element action for providing recent searches option".
Update 06.10.20 - Version 3.15.0
Fixed problem with data loss.
Update 04.06.20 - Version 3.14.0
Fixed bugs with data type retrieval.
Update 26.05.20 - Version 3.13.0
Fixed the bug with Data Type.
Update 15.05.20 - Version 3.12.0
Updated endpoint for the element Algolia Simple Search..
Update 13.05.20 - Version 3.11.0
Fixed data call "Algolia Result" and made description edits..
Update 01.05.20 - Version 3.10.0
Updated demo page.
Update 29.10.19 - Version 3.9.0
Updates and Fixes: Fixed no results in RG, Updated method of returning states. (Check Demo Page).
Update 09.09.19 - Version 3.8.0
Major improvements - V 2.0.
Update 15.08.19 - Version 3.7.0
BugFix - parameter 'aroundLatLng' fixed, from lowercase to camelCase..
Update 14.08.19 - Version 3.6.0
Improvement - (Action Search) added the possibility to search for data by _geoloc property in conformity with Algolia documentation..
Update 13.08.19 - Version 3.5.0
added the possibility to search for data by _geoloc property in conformity with Algolia documentation..
Update 04.05.19 - Version 3.4.0
Minor improvements.
Update 02.05.19 - Version 3.3.0
Improvements.
Update 02.05.19 - Version 3.2.0
minor improvements.
Update 28.02.19 - Version 3.1.0
removed restriction to send only text fields to algolia.
