Search an index
Searches a single index and return matching search results (hits).
This method lets you retrieve up to 1,000 hits.
If you need more, use the browse
operation or increase the paginatedLimitedTo
index setting.
Authorizations
Your Algolia application ID.
Your Algolia API key with the necessary permissions to make the request. Permissions are controlled through access control lists (ACL) and access restrictions. The required ACL to make a request is listed in each endpoint's reference.
Path Parameters
Name of the index on which to perform the operation.
Body
Search parameters as query string.
Search parameters as a URL-encoded query string.
Response
Time the server took to process the request, in milliseconds.
Page of search results to retrieve.
x > 0
Number of results (hits).
Number of pages of results.
Number of hits per page.
1 < x < 1000
Search results (hits).
Hits are records from your index that match the search criteria, augmented with additional attributes, such as, for highlighting.
Search query.
URL-encoded string of all search parameters.
A/B test ID. This is only included in the response for indices that are part of an A/B test.
Variant ID. This is only included in the response for indices that are part of an A/B test.
x > 1
Computed geographical location.
Distance from a central coordinate provided by aroundLatLng
.
Whether certain properties of the search response are calculated exhaustive (exact) or approximated.
See the facetsCount
field of the exhaustive
object in the response.
See the nbHits
field of the exhaustive
object in the response.
See the typo
field of the exhaustive
object in the response.
Facet counts.
Statistics for numerical facets.
Index name used for the query.
Index name used for the query. During A/B testing, the targeted index isn't always the index used by the query.
Warnings about the query.
Number of hits selected and sorted by the relevant sort algorithm.
Post-normalization query string that will be searched.
Experimental. List of processing steps and their times, in milliseconds. You can use this list to investigate performance issues.
Markup text indicating which parts of the original query have been removed to retrieve a non-empty result set.
Redirect results to a URL, this this parameter is for internal use only.
Extra data that can be used in the search UI.
You can use this to control aspects of your search UI, such as, the order of facet names and values without changing your frontend code.
Time the server took to process the request, in milliseconds.
Host name of the server that processed the request.
An object with custom data.
You can store up to 32kB as custom data.
Unique identifier for the query. This is used for click analytics.
Was this page helpful?