algolia / Algoliasearch Client Objc
Licence: other
Algolia Search API Client for iOS & OS X
Stars: ✭ 37
Algolia Search API Client for iOS and OS X
Deprecated
WARNING: Deprecated
In July 2015, we released our Swift API Client, able to work with Swift and Objective-C. As of version 3 (April 2016), Swift has become the reference implementation for both Swift and Objective-C projects.
This Objective-C API Client is no longer under active development. It is still supported for bug fixes, but will not receive new features.
Algolia Search is a hosted full-text, numerical, and faceted search engine capable of delivering realtime results from the first keystroke.
Our Objective-C client lets you easily use the Algolia Search API from your iOS & OS X applications. It wraps the Algolia Search REST API.
Table of Contents
Getting Started
Commands Reference
- Add a new object
- Update an object
- Search
- Search cache
- Multiple queries
- Get an object
- Delete an object
- Delete by query
- Index settings
- List indices
- Delete an index
- Clear an index
- Wait indexing
- Batch writes
- Copy / Move an index
- Backup / Export an index
Setup
Installation
To setup your project, follow these steps:
-
Download and add sources to your project or use cocoapods by adding
pod 'AlgoliaSearch-Client', '~> 3.5'in your Podfile (orpod 'AlgoliaSearch-Client', '~> 2.0'if your are using AFNetworking 1.x in your project) or drop the source folder on your project (If you are not using a Podfile, you will also need to add AFNetworking library in your project). - Add the
#import "ASAPIClient.h"call to your project - Initialize the client with your ApplicationID and API-Key. You can find all of them on your Algolia account.
ASAPIClient *apiClient =
[ASAPIClient apiClientWithApplicationID:@"YourApplicationID" apiKey:@"YourAPIKey"];
Quick Start
In 30 seconds, this quick start tutorial will show you how to index and search objects.
Without any prior configuration, you can start indexing 500 contacts in the contacts index using the following code:
// Load JSON file
NSString *jsonPath = [[NSBundle mainBundle] pathForResource:@"contacts" ofType:@"json"];
NSData* jsonData = [NSData dataWithContentsOfFile:jsonPath];
NSDictionary* dict = [NSJSONSerialization JSONObjectWithData:jsonData options:0 error:nil];
// Load all objects of json file in an index named "contacts"
ASRemoteIndex *index = [apiClient getIndex:@"contacts"];
[index addObjects:dict[@"objects"] success:nil failure:nil];
You can now search for contacts using firstname, lastname, company, etc. (even with typos):
// search by firstname
[index search:[ASQuery queryWithFullTextQuery:@"jimmie"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
// search a firstname with typo
[index search:[ASQuery queryWithFullTextQuery:@"jimie"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
// search for a company
[index search:[ASQuery queryWithFullTextQuery:@"california paint"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
// search for a firstname & company
[index search:[ASQuery queryWithFullTextQuery:@"jimmie paint"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
Settings can be customized to tune the search behavior. For example, you can add a custom sort by number of followers to the already great built-in relevance:
NSArray *customRanking = @[@"desc(followers)"];
NSDictionary *settings = @{@"customRanking": customRanking};
[index setSettings:settings success:nil
failure:^(ASRemoteIndex *index, NSDictionary *settings, NSString *errorMessage) {
NSLog(@"Error when applying settings: %@", errorMessage);
}];
You can also configure the list of attributes you want to index by order of importance (first = most important):
NSArray *customRanking = @[@"lastname", @"firstname", @"company", @"email", @"city", @"address"];
NSDictionary *settings = @{@"attributesToIndex": customRanking};
[index setSettings:settings success:nil
failure:^(ASRemoteIndex *index, NSDictionary *settings, NSString *errorMessage) {
NSLog(@"Error when applying settings: %@", errorMessage);
}];
Since the engine is designed to suggest results as you type, you'll generally search by prefix. In this case the order of attributes is very important to decide which hit is the best:
[index search:[ASQuery queryWithFullTextQuery:@"or"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
[index search:[ASQuery queryWithFullTextQuery:@"jim"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
Guides & Tutorials
Check our online guides:
- Data Formatting
- Import and Synchronize data
- Autocomplete
- Instant search page
- Filtering and Faceting
- Sorting
- Ranking Formula
- Typo-Tolerance
- Geo-Search
- Security
- API-Keys
- REST API
Reference
Add a new object to the Index
Each entry in an index has a unique identifier called objectID. There are two ways to add an entry to the index:
- Using automatic
objectIDassignment. You will be able to access it in the answer. - Supplying your own
objectID.
You don't need to explicitly create an index, it will be automatically created the first time you add an object. Objects are schema less so you don't need any configuration to start indexing. If you wish to configure things, the settings section provides details about advanced settings.
Example with automatic objectID assignment:
NSDictionary *newObject = @{@"firstname": @"Jimmie", @"lastname": @"Barninger"};
[index addObject:newObject
success:^(ASRemoteIndex *index, NSDictionary *object, NSDictionary *result) {
NSLog(@"Object ID: %@", result[@"objectID"]);
} failure:nil];
Example with manual objectID assignment:
NSDictionary *newObject = @{@"firstname": @"Jimmie", @"lastname": @"Barninger"};
[index addObject:newObject withObjectID:@"myID"
success:^(ASRemoteIndex *index, NSDictionary *object, NSString *objectID, NSDictionary *result) {
NSLog(@"Object ID: %@", result[@"objectID"]);
} failure:nil];
Update an existing object in the Index
You have three options when updating an existing object:
- Replace all its attributes.
- Replace only some attributes.
- Apply an operation to some attributes.
Example on how to replace all attributes of an existing object:
NSDictionary *newObject = @{
@"firstname": @"Jimmie",
@"lastname": @"Barninger",
@"city": @"New York"
};
[index saveObject:newObject objectID:@"myID" success:nil failure:nil];
You have many ways to update an object's attributes:
- Set the attribute value
- Add a string or number element to an array
- Remove an element from an array
- Add a string or number element to an array if it doesn't exist
- Increment an attribute
- Decrement an attribute
Example to update only the city attribute of an existing object:
NSDictionary *partialObject = @{@"city": @"San Francisco"};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Example to add a tag:
NSDictionary *operation = @{
@"value": @"MyTag",
@"_operation": @"Add"
};
NSDictionary *partialObject = @{@"_tags": operation};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Example to remove a tag:
NSDictionary *operation = @{
@"value": @"MyTag",
@"_operation": @"Remove"
};
NSDictionary *partialObject = @{@"_tags": operation};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Example to add a tag if it doesn't exist:
NSDictionary *operation = @{
@"value": @"MyTag",
@"_operation": @"AddUnique"
};
NSDictionary *partialObject = @{@"_tags": operation};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Example to increment a numeric value:
NSDictionary *operation = @{
@"value": 42,
@"_operation": @"Increment"
};
NSDictionary *partialObject = @{@"price": operation};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Note: Here we are incrementing the value by 42. To increment just by one, put
value:1.
Example to decrement a numeric value:
NSDictionary *operation = @{
@"value": 42,
@"_operation": @"Decrement"
};
NSDictionary *partialObject = @{@"price": operation};
[index partialUpdateObject:partialObject objectID:@"myID" success:nil failure:nil];
Note: Here we are decrementing the value by 42. To decrement just by one, put
value:1.
Search
To perform a search, you only need to initialize the index and perform a call to the search function.
The search query allows only to retrieve 1000 hits, if you need to retrieve more than 1000 hits for seo, you can use Backup / Retrieve all index content
ASRemoteIndex *index = [apiClient getIndex:@"contacts"];
[index search:[ASQuery queryWithFullTextQuery:@"s"]
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
ASQuery *query = [ASQuery queryWithFullTextQuery:@"s"];
query.attributesToRetrieve = @[@"firstname", @"lastname"];
query.hitsPerPage = 50;
[index search:query
success:^(ASRemoteIndex *index, ASQuery *query, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
The server response will look like:
{
"hits": [
{
"firstname": "Jimmie",
"lastname": "Barninger",
"objectID": "433",
"_highlightResult": {
"firstname": {
"value": "<em>Jimmie</em>",
"matchLevel": "partial"
},
"lastname": {
"value": "Barninger",
"matchLevel": "none"
},
"company": {
"value": "California <em>Paint</em> & Wlpaper Str",
"matchLevel": "partial"
}
}
}
],
"page": 0,
"nbHits": 1,
"nbPages": 1,
"hitsPerPage": 20,
"processingTimeMS": 1,
"query": "jimmie paint",
"params": "query=jimmie+paint&attributesToRetrieve=firstname,lastname&hitsPerPage=50"
}
You can use the following optional arguments on ASQuery class:
Full Text Search Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>fullTextQuery</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The instant search query string, used to set the string you want to search in your index. If no query parameter is set, the textual search will match with all the objects.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>setQueryType</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>prefixLast</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Selects how the query words are interpreted. It can be one of the following values:</p>
-
prefixAll: All query words are interpreted as prefixes. This option is not recommended. -
prefixLast: Only the last word is interpreted as a prefix (default behavior). -
prefixNone: No query word is interpreted as a prefix. This option is not recommended.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>setRemoveWordsIfNoResults</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>none</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This option is used to select a strategy in order to avoid having an empty result page. There are three different options:</p>
-
lastWords: When a query does not return any results, the last word will be added as optional. The process is repeated with n-1 word, n-2 word, ... until there are results. -
firstWords: When a query does not return any results, the first word will be added as optional. The process is repeated with second word, third word, ... until there are results. -
allOptional: When a query does not return any results, a second trial will be made with all words as optional. This is equivalent to transforming the AND operand between query terms to an OR operand. -
none: No specific processing is done when a query does not return any results (default behavior).
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>minWordSizeForApprox1</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>number</strong></em></div><div><em>Default: <strong>4</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The minimum number of characters in a query word to accept one typo in this word.<br/>Defaults to 4.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>minWordSizeForApprox2</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>number</strong></em></div><div><em>Default: <strong>8</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The minimum number of characters in a query word to accept two typos in this word.<br/>Defaults to 8.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>setTypoTolerance</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This option allows you to control the number of typos allowed in the result set:</p>
-
true: The typo tolerance is enabled and all matching hits are retrieved (default behavior). -
false: The typo tolerance is disabled. All results with typos will be hidden. -
min: Only keep results with the minimum number of typos. For example, if one result matches without typos, then all results with typos will be hidden. -
strict: Hits matching with 2 typos are not retrieved if there are some matching without typos.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>allowTyposOnNumericTokens</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, disables typo tolerance on numeric tokens (numbers). Defaults to true.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>ignorePlural</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to true, plural won't be considered as a typo. For example, car and cars, or foot and feet will be considered as equivalent. Defaults to false.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>disableTypoToleranceOnAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>[]</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of attributes on which you want to disable typo tolerance (must be a subset of the <code>attributesToIndex</code> index setting). Attributes are separated with a comma such as <code>"name,address"</code>. You can also use JSON string array encoding such as <code>encodeURIComponent("[\"name\",\"address\"]")</code>. By default, this list is empty.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>restrictSearchableAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>attributesToIndex</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of attributes you want to use for textual search (must be a subset of the <code>attributesToIndex</code> index setting). Attributes are separated with a comma such as <code>"name,address"</code>. You can also use JSON string array encoding such as <code>encodeURIComponent("[\"name\",\"address\"]")</code>. By default, all attributes specified in the <code>attributesToIndex</code> settings are used to search.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>removeStopWords</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Remove stop words from the query <strong>before</strong> executing it. Defaults to <code>false</code>. Use a boolean to enable/disable all 41 supported languages and a comma separated list of iso codes of the languages you want to use consider to enable the stopwords removal on a subset of them (select the one you have in your records). In most use-cases, you shouldn't need to enable this option.</p>
List of 41 supported languages with their associated iso code: Arabic=ar, Armenian=hy, Basque=eu, Bengali=bn, Brazilian=pt-br, Bulgarian=bg, Catalan=ca, Chinese=zh, Czech=cs, Danish=da, Dutch=nl, English=en, Finnish=fi, French=fr, Galician=gl, German=de, Greek=el, Hindi=hi, Hungarian=hu, Indonesian=id, Irish=ga, Italian=it, Japanese=ja, Korean=ko, Kurdish=ku, Latvian=lv, Lithuanian=lt, Marathi=mr, Norwegian=no, Persian (Farsi)=fa, Polish=pl, Portugese=pt, Romanian=ro, Russian=ru, Slovak=sk, Spanish=es, Swedish=sv, Thai=th, Turkish=tr, Ukranian=uk, Urdu=ur
Stop words removal is applied on query words that are not interpreted as a prefix. The behavior depends of the queryType parameter:
queryType=prefixLastmeans the last query word is a prefix and it won’t be considered for stop words removalqueryType=prefixNonemeans no query word are prefix, stop words removal will be applied on all query wordsqueryType=prefixAllmeans all query terms are prefix, stop words won’t be removed
This parameter is useful when you have a query in natural language like “what is a record?”. In this case, before executing the query, we will remove “what”, “is” and “a” in order to just search for “record”. This removal will remove false positive because of stop words, especially when combined with optional words. For most use cases, it is better to not use this feature as people search by keywords on search engines.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>exactOnSingleWordQuery</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>attribute</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This parameter control how the <code>exact</code> ranking criterion is computed when the query contains one word. There is three different values:</p>
none: no exact on single word queryword: exact set to 1 if the query word is found in the record. The query word needs to have at least 3 chars and not be part of our stop words dictionaryattribute(default): exact set to 1 if there is an attribute containing a string equals to the query
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>alternativesAsExact</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>["ignorePlurals", "singleWordSynonym"]</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the list of approximation that should be considered as an exact match in the ranking formula:</p>
ignorePlurals: alternative words added by the ignorePlurals featuresingleWordSynonym: single-word synonym (For example "NY" = "NYC")multiWordsSynonym: multiple-words synonym (For example "NY" = "New York")
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>advancedSyntax</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>0 (false)</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Enables the advanced query syntax. Defaults to 0 (false).</p>
-
Phrase query: A phrase query defines a particular sequence of terms. A phrase query is built by Algolia's query parser for words surrounded by
". For example,"search engine"will retrieve records havingsearchnext toengineonly. Typo tolerance is disabled on phrase queries. -
Prohibit operator: The prohibit operator excludes records that contain the term after the
-symbol. For example,search -enginewill retrieve records containingsearchbut notengine.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>analytics</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, this query will not be taken into account in the analytics feature. Defaults to true.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>synonyms</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, this query will not use synonyms defined in the configuration. Defaults to true.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>replaceSynonymsInHighlight</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, words matched via synonym expansion will not be replaced by the matched synonym in the highlight results. Defaults to true.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>optionalWords</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>[]</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>An array of strings that contain the list of words that should be considered as optional when found in the query.</p>
</td>
</tr>
Pagination Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>page</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div><div><em>Default: <strong>0</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Pagination parameter used to select the page to retrieve.<br/>Page is zero based and defaults to 0. Thus, to retrieve the 10th page you need to set <code>page=9</code>.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>hitsPerPage</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div><div><em>Default: <strong>20</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Pagination parameter used to select the number of hits per page. Defaults to 20.</p>
</td>
</tr>
Geo-search Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchAroundLatitude:longitude:</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>float,float</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search for entries around a given latitude/longitude.<br/>The maximum distance is automatically guessed depending of the density of the area but you also manually specify the maximum distance in meters with the <code>maxDist</code> parameter.<br/>At indexing, you should specify the geo location of an object with the <code>_geoloc</code> attribute in the form <code>{"_geoloc":{"lat":48.853409, "lng":2.348800}}</code>.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchAroundLatitude:longitude:maxDist:precision</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search for entries around a given latitude/longitude with a given precision for ranking. For example, if you set aroundPrecision=100, the distances will be considered by ranges of 100m, for example all distances 0 and 100m will be considered as identical for the "geo" ranking parameter.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchAroundLatitudeLongitudeViaIP</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search for entries around the latitude/longitude automatically computed from user IP address.<br/>The radius is automatically guessed based on density but you can also specify it manually with the <code>maxDist</code> parameter (optional).<br/>At indexing, you should specify the geo location of an object with the <code>_geoloc</code> attribute in the form <code>{"_geoloc":{"lat":48.853409, "lng":2.348800}}</code>.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchAroundLatitudeLlongitude:precision</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search for entries around a latitude/longitude automatically computed from user IP address with a given precision for ranking. For example if you set precision=100, two objects that are a distance of less than 100 meters will be considered as identical for the "geo" ranking parameter.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchInsideBoundingBoxWithLatitudeP1:longitudeP1:latitudeP2:longitudeP2</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search entries inside a given area defined by the two extreme points of a rectangle (defined by 4 floats: p1Lat,p1Lng,p2Lat,p2Lng).<br/>For example, <code>searchInsideBoundingBoxWithLatitudeP1(47.3165, 4.9665, 47.3424, 5.0201)</code>).<br/>At indexing, you should specify geoloc of an object with the _geoloc attribute (in the form <code>"_geoloc":{"lat":48.853409, "lng":2.348800}</code> or <code>"_geoloc":[{"lat":48.853409, "lng":2.348800},{"lat":48.547456, "lng":2.972075}]</code> if you have several geo-locations in your record). You can use several bounding boxes (OR) by passing more than 4 values. For example instead of having 4 values you can pass 8 to search inside the UNION of two bounding boxes.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>searchInsidePolygon:</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Search entries inside a given area defined by a set of points (defined by a minimum of 6 floats: p1Lat,p1Lng,p2Lat,p2Lng,p3Lat,p3Long).<br/>For example <code>searchInsidePolygon(47.3165, 4.9665, 47.3424, 5.0201, 47.32, 4.98)</code>).<br/>At indexing, you should specify geoloc of an object with the _geoloc attribute (in the form <code>"_geoloc":{"lat":48.853409, "lng":2.348800}</code> or <code>"_geoloc":[{"lat":48.853409, "lng":2.348800},{"lat":48.547456, "lng":2.972075}]</code> if you have several geo-locations in your record).</p>
</td>
</tr>
Parameters to Control Results Content
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToRetrieve</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of attributes you want to retrieve in order to minimize the size of the JSON answer. By default, all attributes are retrieved. You can also use <code>*</code> to retrieve all values when an <strong>attributesToRetrieve</strong> setting is specified for your index.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToHighlight</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of attributes you want to highlight according to the query. If an attribute has no match for the query, the raw value is returned. By default, all indexed attributes are highlighted. You can use <code>*</code> if you want to highlight all attributes. A matchLevel is returned for each highlighted attribute and can contain:</p>
-
full: If all the query terms were found in the attribute. -
partial: If only some of the query terms were found. -
none: If none of the query terms were found.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToSnippet</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of attributes to snippet alongside the number of words to return (syntax is <code>attributeName:nbWords</code>). By default, no snippet is computed.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>getRankingInfo</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to YES, the result hits will contain ranking information in the <strong>_rankingInfo</strong> attribute.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>setHighlightingTags</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string, string</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the string that is inserted before the highlighted parts in the query result (defaults to "<em>") and the string that is inserted after the highlighted parts in the query result (defaults to "</em>")..</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>setSnippetEllipsisText</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>String used as an ellipsis indicator when a snippet is truncated (defaults to empty).</p>
</td>
</tr>
Numeric Search Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>numericFilters</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>A string that contains the comma separated list of numeric filters you want to apply. The filter syntax is <code>attributeName</code> followed by <code>operand</code> followed by <code>value</code>. Supported operands are <code><</code>, <code><=</code>, <code>=</code>, <code>></code> and <code>>=</code>.</p>
</td>
</tr>
You can easily perform range queries via the : operator. This is equivalent to combining a >= and <= operand. For example, numericFilters=price:10 to 1000.
You can also mix OR and AND operators. The OR operator is defined with a parenthesis syntax. For example, (code=1 AND (price:[0-100] OR price:[1000-2000])) translates to encodeURIComponent("code=1,(price:0 to 100,price:1000 to 2000)").
You can also use a string array encoding (for example numericFilters: ["price>100","price<1000"]).
Category Search Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>tagFilters</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Filter the query by a set of tags. You can AND tags by separating them with commas. To OR tags, you must add parentheses. For example, <code>tagFilters=tag1,(tag2,tag3)</code> means <em>tag1 AND (tag2 OR tag3)</em>. You can also use a string array encoding. For example, <code>tagFilters: ["tag1",["tag2","tag3"]]</code> means <em>tag1 AND (tag2 OR tag3)</em>. Negations are supported via the <code>-</code> operator, prefixing the value. For example: <code>tagFilters=tag1,-tag2</code>.</p>
At indexing, tags should be added in the _tags attribute of objects. For example {"_tags":["tag1","tag2"]}.
</td>
</tr>
Faceting Parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>facetFilters</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Filter the query with a list of facets. Facets are separated by commas and is encoded as <code>attributeName:value</code>. To OR facets, you must add parentheses. For example: <code>facetFilters=(category:Book,category:Movie),author:John%20Doe</code>. You can also use a string array encoding. For example, <code>[["category:Book","category:Movie"],"author:John%20Doe"]</code>.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>facets</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of object attributes that you want to use for faceting. For each of the declared attributes, you'll be able to retrieve a list of the most relevant facet values, and their associated count for the current query.</p>
Attributes are separated by a comma. For example, "category,author". You can also use JSON string array encoding. For example, ["category","author"]. Only the attributes that have been added in attributesForFaceting index setting can be used in this parameter. You can also use * to perform faceting on all attributes specified in attributesForFaceting. If the number of results is important, the count can be approximate, the attribute exhaustiveFacetsCount in the response is true when the count is exact.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>maxValuesPerFacet</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Limit the number of facet values returned for each facet. For example, <code>maxValuesPerFacet=10</code> will retrieve a maximum of 10 values per facet.</p>
</td>
</tr>
Unified Filter Parameter (SQL - like)
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>filters</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Filter the query with numeric, facet or/and tag filters. The syntax is a SQL like syntax, you can use the OR and AND keywords. The syntax for the underlying numeric, facet and tag filters is the same than in the other filters:
available=1 AND (category:Book OR NOT category:Ebook) AND _tags:public
date: 1441745506 TO 1441755506 AND inStock > 0 AND author:"John Doe"
If no attribute name is specified, the filter applies to _tags. For example: public OR user_42 will translate to _tags:public OR _tags:user_42.
The list of keywords is:
-
OR: create a disjunctive filter between two filters. -
AND: create a conjunctive filter between two filters. -
TO: used to specify a range for a numeric filter. -
NOT: used to negate a filter. The syntax with the-isn’t allowed.
</td>
</tr>
Warning:
- Like for the other filters (for performance reasons), it's not possible to have FILTER1 OR (FILTER2 AND FILTER3).
- It's not possible to mix different categories of filters inside an OR like: num=3 OR tag1 OR facet:value
- It's not possible to negate a group, it's only possible to negate a filter: NOT(FILTER1 OR (FILTER2) is not allowed.
Distinct Parameter
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>distinct</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to YES, enables the distinct feature, disabled by default, if the <code>attributeForDistinct</code> index setting is set. This feature is similar to the SQL "distinct" keyword. When enabled in a query with the <code>distinct=1</code> parameter, all hits containing a duplicate value for the attributeForDistinct attribute are removed from results. For example, if the chosen attribute is <code>show_name</code> and several hits have the same value for <code>show_name</code>, then only the best one is kept and the others are removed.</p>
</td>
</tr>
To get a full understanding of how Distinct works, you can have a look at our guide on distinct.
Search cache
You can easily cache the results of the search queries by enabling the search cache. The results will be cached during a defined amount of time (default: 2 min). There is no pre-caching mechanism but you can simulate it by making a preemptive search query.
By default, the cache is disabled.
[myIndex enableSearchCache];
Or:
[myIndex enableSearchCacheWithExpiringTimeInterval:300];
Multiple queries
You can send multiple queries with a single API call using a batch of queries:
// perform 3 queries in a single API call:
// - 1st query targets index `categories`
// - 2nd and 3rd queries target index `products`
NSArray *queries = @[
@{@"indexName": @"categories", @"query": anASQueryObject},
@{@"indexName": @"products", @"query": anotherASQueryObject},
@{@"indexName": @"products", @"query": anotherASQueryObject}
];
[client multipleQueries:queries
success:^(ASAPIClient *client, NSArray *queries, NSDictionary *result) {
NSLog(@"Result: %@", result);
} failure:nil];
The resulting JSON answer contains a results array storing the underlying queries answers. The answers order is the same than the requests order.
You can specify a strategy parameter to optimize your multiple queries:
-
none: Execute the sequence of queries until the end. -
stopIfEnoughMatches: Execute the sequence of queries until the number of hits is reached by the sum of hits.
Get an object
You can easily retrieve an object using its objectID and optionally specify a comma separated list of attributes you want:
// Retrieves all attributes
[index getObject:@"myID"
success:^(ASRemoteIndex *index, NSString *objectID, NSDictionary *result) {
NSLog(@"Object: %@", result);
} failure:nil];
// Retrieves only the firstname attribute
[index getObject:@"myID" attributesToRetrieve:@[@"firstname"]
success:^(ASRemoteIndex *index, NSString *objectID, NSArray *attributesToRetrieve, NSDictionary *result) {
NSLog(@"Object: %@", result);
} failure:nil];
You can also retrieve a set of objects:
[index getObjects:@[@"myID1", @"myID2"]
success:^(ASRemoteIndex *index, NSArray *objectIDs, NSDictionary *result) {
// do something
} failure:nil];
Delete an object
You can delete an object using its objectID:
[index deleteObject:@"myID" success:nil failure:nil];
Delete by query
You can delete all objects matching a single query with the following code. Internally, the API client performs the query, deletes all matching hits, and waits until the deletions have been applied.
ASQuery *query = /* [...] */;
[index deleteByQuery:query success:nil failure:nil];
Index Settings
You can easily retrieve or update settings:
[index getSettings:^(ASRemoteIndex *index, NSDictionary *result) {
NSLog(@"Settings: %@", result);
} failure:nil];
NSArray *customRanking = @[@"desc(followers)", @"asc(name)"];
NSDictionary *settings = @{@"customRanking": customRanking};
[index setSettings:settings success:nil failure:nil];
Indexing parameters
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToIndex</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of attributes you want index (i.e. to make searchable).</p>
If set to null, all textual and numerical attributes of your objects are indexed. Make sure you updated this setting to get optimal results.
This parameter has two important uses:
-
Limit the attributes to index.
For example, if you store the URL of a picture, you want to store it and be able to retrieve it, but you probably don't want to search in the URL. -
Control part of the ranking.
Matches in attributes at the beginning of the list will be considered more important than matches in attributes further down the list. In one attribute, matching text at the beginning of the attribute will be considered more important than text after. You can disable this behavior if you add your attribute insideunordered(AttributeName). For example,attributesToIndex: ["title", "unordered(text)"]. You can decide to have the same priority for two attributes by passing them in the same string using a comma as a separator. For exampletitleandalternative_titlehave the same priority in this example, which is different than text priority:attributesToIndex:["title,alternative_title", "text"]. To get a full description of how the Ranking works, you can have a look at our Ranking guide. -
numericAttributesToIndex: (array of strings) All numerical attributes are automatically indexed as numerical filters (allowing filtering operations like
<and<=). If you don't need filtering on some of your numerical attributes, you can specify this list to speed up the indexing.
If you only need to filter on a numeric value with the operator '=', you can speed up the indexing by specifying the attribute withequalOnly(AttributeName). The other operators will be disabled.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesForFaceting</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of fields you want to use for faceting. All strings in the attribute selected for faceting are extracted and added as a facet. If set to null, no attribute is used for faceting.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributeForDistinct</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The name of the attribute used for the <code>Distinct</code> feature. This feature is similar to the SQL "distinct" keyword. When enabled in queries with the <code>distinct=1</code> parameter, all hits containing a duplicate value for this attribute are removed from the results. For example, if the chosen attribute is <code>show_name</code> and several hits have the same value for <code>show_name</code>, then only the first one is kept and the others are removed from the results. To get a full understanding of how <code>Distinct</code> works, you can have a look at our <a href="https://www.algolia.com/doc/search/distinct">guide on distinct</a>.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>ranking</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Controls the way results are sorted.</p>
We have nine available criteria:
-
typo: Sort according to number of typos. -
geo: Sort according to decreasing distance when performing a geo location based search. -
words: Sort according to the number of query words matched by decreasing order. This parameter is useful when you use theoptionalWordsquery parameter to have results with the most matched words first. -
proximity: Sort according to the proximity of the query words in hits. -
attribute: Sort according to the order of attributes defined by attributesToIndex. -
exact:- If the user query contains one word: sort objects having an attribute that is exactly the query word before others. For example, if you search for the TV show "V", you want to find it with the "V" query and avoid getting all popular TV shows starting by the letter V before it.
- If the user query contains multiple words: sort according to the number of words that matched exactly (not as a prefix).
-
custom: Sort according to a user defined formula set in thecustomRankingattribute. -
asc(attributeName): Sort according to a numeric attribute using ascending order.attributeNamecan be the name of any numeric attribute in your records (integer, double or boolean). -
desc(attributeName): Sort according to a numeric attribute using descending order.attributeNamecan be the name of any numeric attribute in your records (integer, double or boolean).
The standard order is["typo", "geo", "words", "proximity", "attribute", "exact", "custom"]. To get a full description of how the Ranking works, you can have a look at our Ranking guide.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>customRanking</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Lets you specify part of the ranking.</p>
The syntax of this condition is an array of strings containing attributes prefixed by the asc (ascending order) or desc (descending order) operator. For example, "customRanking" => ["desc(population)", "asc(name)"].
To get a full description of how the Custom Ranking works, you can have a look at our Ranking guide.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>queryType</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>prefixLast</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Select how the query words are interpreted. It can be one of the following values:</p>
-
prefixAll: All query words are interpreted as prefixes. -
prefixLast: Only the last word is interpreted as a prefix (default behavior). -
prefixNone: No query word is interpreted as a prefix. This option is not recommended.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>separatorsToIndex</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>empty</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the separators (punctuation characters) to index. By default, separators are not indexed. Use <code>+#</code> to be able to search Google+ or C#.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>slaves</code></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of indices on which you want to replicate all write operations. In order to get response times in milliseconds, we pre-compute part of the ranking during indexing. If you want to use different ranking configurations depending of the use case, you need to create one index per ranking configuration. This option enables you to perform write operations only on this index and automatically update slave indices with the same operations.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>unretrievableAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>empty</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The list of attributes that cannot be retrieved at query time. This feature allows you to have attributes that are used for indexing and/or ranking but cannot be retrieved. Defaults to null. Warning: for testing purposes, this setting is ignored when you're using the ADMIN API Key.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>allowCompressionOfIntegerArray</code></div>
<div class="client-readme-param-meta"><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Allows compression of big integer arrays. In data-intensive use-cases, we recommended enabling this feature and then storing the list of user IDs or rights as an integer array. When enabled, the integer array is reordered to reach a better compression ratio. Defaults to false.</p>
</td>
</tr>
Query expansion
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>synonyms</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of array of string considered as equals</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>For example, you may want to retrieve the <strong>black ipad</strong> record when your users are searching for <strong>dark ipad</strong>, even if the word <strong>dark</strong> is not part of the record. To do this, you need to configure <strong>black</strong> as a synonym of <strong>dark</strong>. For example, <code>"synomyms": [ [ "black", "dark" ], [ "small", "little", "mini" ], ... ]</code>. The Synonym feature also supports multi-words expressions like <code>"synonyms": [ ["NYC", "New York City"] ]</code></p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>placeholders</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>hash of array of words</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This is an advanced use-case to define a token substitutable by a list of words without having the original token searchable. It is defined by a hash associating placeholders to lists of substitutable words. For example, <code>"placeholders": { "<streetnumber>": ["1", "2", "3", ..., "9999"]}</code> would allow it to be able to match all street numbers. We use the <code>< ></code> tag syntax to define placeholders in an attribute. For example:</p>
- Push a record with the placeholder:
{ "name" : "Apple Store", "address" : "<streetnumber> Opera street, Paris" }. - Configure the placeholder in your index settings:
"placeholders": { "<streetnumber>" : ["1", "2", "3", "4", "5", ... ], ... }.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>disableTypoToleranceOnWords</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify a list of words on which automatic typo tolerance will be disabled.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>disableTypoToleranceOnAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of attributes on which you want to disable typo tolerance (must be a subset of the <code>attributesToIndex</code> index setting). By default the list is empty.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>disablePrefixOnAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of attributes on which you want to disable prefix matching (must be a subset of the <code>attributesToIndex</code> index setting). This setting is useful on attributes that contain string that should not be matched as a prefix (for example a product SKU). By default the list is empty.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>disableExactOnAttributes</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>List of attributes on which you want to disable the computation of <code>exact</code> criteria (must be a subset of the <code>attributesToIndex</code> index setting). By default the list is empty.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>altCorrections</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>object array</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify alternative corrections that you want to consider. Each alternative correction is described by an object containing three attributes:</p>
- word: The word to correct.
- correction: The corrected word.
- nbTypos The number of typos (1 or 2) that will be considered for the ranking algorithm (1 typo is better than 2 typos).
For example "altCorrections": [ { "word" : "foot", "correction": "feet", "nbTypos": 1 }, { "word": "feet", "correction": "foot", "nbTypos": 1 } ].
</td>
</tr>
Default query parameters (can be overwritten by queries)
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>minWordSizefor1Typo</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div><div><em>Default: <strong>4</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The minimum number of characters needed to accept one typo (default = 4).</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>minWordSizefor2Typos</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div><div><em>Default: <strong>8</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The minimum number of characters needed to accept two typos (default = 8).</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>hitsPerPage</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div><div><em>Default: <strong>10</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>The number of hits per page (default = 10).</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToRetrieve</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Default list of attributes to retrieve in objects. If set to null, all attributes are retrieved.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToHighlight</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Default list of attributes to highlight. If set to null, all indexed attributes are highlighted.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>attributesToSnippet</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Default list of attributes to snippet alongside the number of words to return (syntax is <code>attributeName:nbWords</code>).<br/>By default, no snippet is computed. If set to null, no snippet is computed.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>highlightPreTag</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the string that is inserted before the highlighted parts in the query result (defaults to <code><em></code>).</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>highlightPostTag</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the string that is inserted after the highlighted parts in the query result (defaults to <code></em></code>).</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>optionalWords</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>array of strings</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify a list of words that should be considered optional when found in the query.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>allowTyposOnNumericTokens</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>boolean</strong></em></div><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, disable typo-tolerance on numeric tokens (=numbers) in the query word. For example the query <code>"304"</code> will match with <code>"30450"</code>, but not with <code>"40450"</code> that would have been the case with typo-tolerance enabled. Can be very useful on serial numbers and zip codes searches. Defaults to false.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>ignorePlurals</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>boolean</strong></em></div><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to true, singular/plural forms won’t be considered as typos (for example car/cars and foot/feet will be considered as equivalent). Defaults to false.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>advancedSyntax</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer (0 or 1)</strong></em></div><div><em>Default: <strong>0</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Enable the advanced query syntax. Defaults to 0 (false).</p>
Phrase query: a phrase query defines a particular sequence of terms. A phrase query is build by Algolia's query parser for words surrounded by
". For example,"search engine"will retrieve records havingsearchnext toengineonly. Typo-tolerance is disabled on phrase queries.Prohibit operator: The prohibit operator excludes records that contain the term after the
-symbol. For examplesearch -enginewill retrieve records containingsearchbut notengine.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>replaceSynonymsInHighlight</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>boolean</strong></em></div><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>If set to false, words matched via synonyms expansion will not be replaced by the matched synonym in the highlighted result. Defaults to true.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>maxValuesPerFacet</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Limit the number of facet values returned for each facet. For example: <code>maxValuesPerFacet=10</code> will retrieve max 10 values per facet.</p>
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>distinct</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>integer (0 or 1)</strong></em></div><div><em>Default: <strong>0</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Enable the distinct feature (disabled by default) if the <code>attributeForDistinct</code> index setting is set. This feature is similar to the SQL "distinct" keyword: when enabled in a query with the <code>distinct=1</code> parameter, all hits containing a duplicate value for the<code>attributeForDistinct</code> attribute are removed from results. For example, if the chosen attribute is <code>show_name</code> and several hits have the same value for <code>show_name</code>, then only the best one is kept and others are removed.</p>
To get a full understanding of how Distinct works, you can have a look at our guide on distinct.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>typoTolerance</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div><div><em>Default: <strong>true</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This setting has four different options:</p>
true:activate the typo-tolerance (default value).false:disable the typo-tolerancemin:keep only results with the lowest number of typos. For example if one result matches without typos, then all results with typos will be hidden.strict:if there is a match without typo, then all results with 2 typos or more will be removed.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>removeStopWords</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>boolean or string array</strong></em></div><div><em>Default: <strong>false</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Remove stop words from the query <strong>before</strong> executing it. Defaults to <code>false</code>. Use a boolean to enable/disable all 41 supported languages and an array of string listing the iso codes of the languages you want to use consider to enable the stop words removal on a subset of them (select the one you have in your records).</p>
List of 41 supported languages with their associated iso code: Arabic=ar, Armenian=hy, Basque=eu, Bengali=bn, Brazilian=pt-br, Bulgarian=bg, Catalan=ca, Chinese=zh, Czech=cs, Danish=da, Dutch=nl, English=en, Finnish=fi, French=fr, Galician=gl, German=de, Greek=el, Hindi=hi, Hungarian=hu, Indonesian=id, Irish=ga, Italian=it, Japanese=ja, Korean=ko, Kurdish=ku, Latvian=lv, Lithuanian=lt, Marathi=mr, Norwegian=no, Persian (Farsi)=fa, Polish=pl, Portugese=pt, Romanian=ro, Russian=ru, Slovak=sk, Spanish=es, Swedish=sv, Thai=th, Turkish=tr, Ukranian=uk, Urdu=ur.
Stop words removal is applied on query words that are not interpreted as a prefix. The behavior depends of the queryType setting:
queryType=prefixLastmeans the last query word is a prefix and it won’t be considered for stop words removalqueryType=prefixNonemeans no query word are prefix, stop words removal will be applied on all query wordsqueryType=prefixAllmeans all query terms are prefix, stop words won’t be removed
This index setting is useful when you have queries in natural language like “what is a record?”. In this case, before executing the query, we will remove “what”, “is” and “a” in order to just search for “record”. This removal will remove false positive because of stop words. For most use cases, it is better to not use this feature as people search by keywords on search engines.
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>exactOnSingleWordQuery</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string</strong></em></div><div><em>Default: <strong>attribute</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>This parameter controls how the <code>exact</code> ranking criterion is computed when the query contains one word. There is three different values:</p>
none: noexacton single word queryword:exactset to 1 if the query word is found in the record. The query word needs to have at least 3 chars and not be part of our stop words dictionaryattribute(default): exact set to 1 if there is an attribute containing a string equals to the query
</td>
</tr>
<tr>
<td valign='top'>
<div class='client-readme-param-container'>
<div class='client-readme-param-container-inner'>
<div class='client-readme-param-name'><code>alternativesAsExact</code></div>
<div class="client-readme-param-meta"><div><em>Type: <strong>string array</strong></em></div><div><em>Default: <strong>["ignorePlurals", "singleWordSynonym"]</strong></em></div></div>
</div>
</div>
</td>
<td class='client-readme-param-content'>
<p>Specify the list of approximation that should be considered as an exact match in the ranking formula:</p>
ignorePlurals: alternative words added by the ignorePlurals featuresingleWordSynonym: single-word synonym (For example "NY" = "NYC")multiWordsSynonym: multiple-words synonym (For example "NY" = "New York")
</td>
</tr>
List indices
You can list all your indices along with their associated information (number of entries, disk size, etc.) with the listIndexes method:
[client listIndexes:^(ASAPIClient *client, NSDictionary *result) {
NSLog(@"Indexes: %@", result);
} failure:nil];
Delete an index
You can delete an index using its name:
[client deleteIndex:@"contacts" success:nil
failure:^(ASAPIClient *client, NSString *indexName, NSString *errorMessage) {
NSLog(@"Could not delete: %@", errorMessage);
}];
Clear an index
You can delete the index contents without removing settings and index specific API keys by using the clearIndex command:
[index clearIndex:nil
failure:^(ASRemoteIndex *index, NSString *errorMessage) {
NSLog(@"Could not clear index: %@", errorMessage);
}];
Wait indexing
All write operations in Algolia are asynchronous by design.
It means that when you add or update an object to your index, our servers will
reply to your request with a taskID as soon as they understood the write
operation.
The actual insert and indexing will be done after replying to your code.
You can wait for a task to complete using the waitTask method on the taskID returned by a write operation.
For example, to wait for indexing of a new object:
[index addObject:newObject
success:^(ASRemoteIndex *index, NSDictionary *object, NSDictionary *result) {
// Wait task
[index waitTask:result[@"taskID"]
success:^(ASRemoteIndex *index, NSString *taskID, NSDictionary *result) {
NSLog(@"New object is indexed");
} failure:nil];
} failure:nil];
If you want to ensure multiple objects have been indexed, you only need to check
the biggest taskID.
Batch writes
You may want to perform multiple operations with one API call to reduce latency. We expose four methods to perform batch operations:
-
addObjects: Add an array of objects using automaticobjectIDassignment. -
saveObjects: Add or update an array of objects that contains anobjectIDattribute. -
deleteObjects: Delete an array of objectIDs. -
partialUpdateObjects: Partially update an array of objects that contain anobjectIDattribute (only specified attributes will be updated).
Example using automatic objectID assignment:
NSDictionary *obj1 = @{@"firstname": @"Jimmie", @"lastname": @"Barninger"};
NSDictionary *obj2 = @{@"firstname": @"Warren", @"lastname": @"Speach"};
[index addObjects:@[obj1, obj2]
success:^(ASRemoteIndex *index, NSArray *objects, NSDictionary *result) {
NSLog(@"Object IDs: %@", result);
} failure:nil];
Example with user defined objectID (add or update):
NSDictionary *obj1 = @{@"firstname": @"Jimmie", @"lastname": @"Barninger", @"objectID": @"myID1"};
NSDictionary *obj2 = @{@"firstname": @"Warren", @"lastname": @"Speach", @"objectID": @"myID2"};
[index saveObjects:@[obj1, obj2]
success:^(ASRemoteIndex *index, NSArray *objects, NSDictionary *result) {
NSLog(@"Object IDs: %@", result);
} failure:nil];
Example that deletes a set of records:
[index deleteObjects:@[@"myID1", @"myID2"] success:nil failure:nil];
Example that updates only the firstname attribute:
NSDictionary *obj1 = @{@"firstname": @"Jimmie", @"objectID": @"myID1"};
NSDictionary *obj2 = @{@"firstname": @"Warren", @"objectID": @"myID2"};
[index partialUpdateObjects:@[obj1, obj2]
success:^(ASRemoteIndex *index, NSArray *objects, NSDictionary *result) {
NSLog(@"Object IDs: %@", result);
} failure:nil];
If you have one index per user, you may want to perform a batch operations across severals indexes. We expose a method to perform this type of batch:
NSArray *requests = @[
@{@"action": @"addObject", @"indexName": @"index1", @"body": @{@"firstname": @"Jimmie", @"lastname": @"Barninger"}},
@{@"action": @"addObject", @"indexName": @"index2", @"body": @{@"firstname": @"Warren", @"lastname": @"Speach"}}
];
[client batch:requests
success:^(ASRemoteIndex *index, NSArray *request, NSDictionary *result) {
NSLog(@"Object IDs: %@", result);
} failure:nil];
The attribute action can have these values:
- addObject
- updateObject
- partialUpdateObject
- partialUpdateObjectNoCreate
- deleteObject
Copy / Move an index
You can easily copy or rename an existing index using the copy and move commands.
Note: Move and copy commands overwrite the destination index.
// Rename MyIndex in MyIndexNewName
[apiClient moveIndex:@"MyIndex" to:@"MyIndexNewName"
success:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSDictionary *result) {
NSLog(@"Move Success: %@", result);
} failure:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSString *errorMessage) {
NSLog(@"Move Failure: %@", errorMessage);
}];
// Copy MyIndex in MyIndexCopy
[apiClient copyIndex:@"MyIndex" to:@"MyIndexCopy"
success:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSDictionary *result) {
NSLog(@"Copy Success: %@", result);
} failure:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSString *errorMessage) {
NSLog(@"Copy Failure: %@", errorMessage);
}];
The move command is particularly useful if you want to update a big index atomically from one version to another. For example, if you recreate your index MyIndex each night from a database by batch, you only need to:
- Import your database into a new index using batches. Let's call this new index
MyNewIndex. - Rename
MyNewIndextoMyIndexusing the move command. This will automatically override the old index and new queries will be served on the new one.
// Rename MyNewIndex in MyIndex (and overwrite it)
[apiClient moveIndex:@"MyNewIndex" to:@"MyIndex"
success:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSDictionary *result) {
NSLog(@"Move Success: %@", result);
} failure:^(ASAPIClient *client, NSString *srcIndexName, NSString *dstIndexName, NSString *errorMessage) {
NSLog(@"Move Failure: %@", errorMessage);
}];
Backup / Export an index
The search method cannot return more than 1,000 results. If you need to
retrieve all the content of your index (for backup, SEO purposes or for running
a script on it), you should use the browse method instead. This method lets
you retrieve objects beyond the 1,000 limit.
This method is optimized for speed. To make it fast, distinct, typo-tolerance, word proximity, geo distance and number of matched words are disabled. Results are still returned ranked by attributes and custom ranking.
It will return a cursor alongside your data, that you can then use to retrieve
the next chunk of your records.
You can specify custom parameters (like page or hitsPerPage) on your first
browse call, and these parameters will then be included in the cursor. Note
that it is not possible to access records beyond the 1,000th on the first call.
Example:
// Iterate with a filter over the index
[index browseWithQuery:query block:^(ASBrowseIterator *iterator, BOOL end, NSString *error) {
// Retrieve the next cursor from the browse method
NSLog(iterator.cursor);
if (error != nil) {
// Handle errors
} else if (end) {
// End of the index
} else {
// Do something
[iterator next];
}
}];
Note that the project description data, including the texts, logos, images, and/or trademarks,
for each open source project belongs to its rightful owner.
If you wish to add or remove any projects, please contact us at [email protected].