Search rules
settings
ACL
We released a new version of the PHP API client in public beta. Read the beta documentation for more information.
We released a new version of the JavaScript API client in public beta. Read the beta documentation for more information.
We released a new version of the Java API client in public beta. Read the beta documentation for more information.
You’re currently reading the JavaScript API client v4 documentation. Check the migration guide to learn how to upgrade from v3 to v4. You can still access the v3 documentation.
You’re currently reading the Ruby API client v2 documentation. Check the migration guide to learn how to upgrade from v1 to v2. You can still access the v1 documentation.
About this method
Search for rules matching various criteria.
Examples
Read the Algolia CLI documentation for more information.
1
2
3
$response = $index->searchRules('something', [
'enabled' => true
]);
Parameters
Parameter | Description |
---|---|
query
|
type: string
default: ""
Optional
Full text query. |
anchoring
|
type: string|enum
default: all anchoring
Optional
When specified, restricts matches to rules with a specific anchoring type. When omitted, all anchoring types may match. One of the following values:
|
context
|
type: string
default: Any context
Optional
Restricts matches to contextual rules with a specific context (exact match). |
page
|
type: integer
default: 0
Optional
Requested page (zero-based). |
hitsPerPage
|
type: integer
default: 20
Optional
Maximum number of hits in a page. Minimum is 1, maximum is 1000. |
enabled
|
type: boolean
default: none
Optional
When specified, restricts matches to rules with a specific |
requestOptions
|
type: key/value mapping
default: No request options
Optional
A mapping of |
Response
This section shows the JSON response returned by the API.
Each API client encapsulates this response inside objects specific to the programming language,
so that the actual response might be different.
You can view the response by using the getLogs
method.
Don’t rely on the order of attributes in the response, as JSON doesn’t guarantee the ordering of keys in objects.
JSON format
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
{
"hits":[
{
"conditions":[{
"pattern":"smartphone",
"anchoring":"contains"
}],
"consequence":{
"params":{
"filters":"category = 1"
}
},
"objectID":"a-rule-id",
"_highlightResult":{
"conditions":[{
"pattern":{
"value":"<b>s<\/b>martphone",
"matchLevel":"full",
"fullyHighlighted":false,
"matchedWords":[
"s"
]
}],
"anchoring":{
"value":"contains",
"matchLevel":"none",
"matchedWords":[
]
}
},
"consequence":{
"params":{
"filters":{
"value":"category = 1",
"matchLevel":"none",
"matchedWords":[
]
}
}
}
}
}
],
"nbHits":1,
"page":0,
"nbPages":1
}
Field | Description |
---|---|
hits
|
list of rule
Rule objects matched by the search query (see Rule Schema).
Highlighting is provided through the standard mechanism ( |
nbHits
|
integer
Total number of rules matching the query. |
page
|
integer
Returned page number (zero-based). |
nbPages
|
integer
Total number of pages. |