Create or update a batch of Recommend Rules
Create or update a batch of Recommend Rules
objectID already exists.
You may also specify true for clearExistingRules, in which case the batch will atomically replace all the existing Recommend Rules.
Recommend Rules are similar to Search Rules, except that the conditions and consequences apply to a source item instead of a query. The main differences are the following:
- Conditions
patternandanchoringare unavailable. - Condition
filterstriggers if the source item matches the specified filters. - Condition
filtersaccepts numeric filters. - Consequence
paramsonly covers filtering parameters. - Consequence
automaticFacetFiltersdoesn’t require a facet value placeholder (it tries to match the data source item’s attributes instead).
editSettingsAuthorizations
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.
"ALGOLIA_INDEX_NAME"
related-products, bought-together, trending-facets, trending-items Body
Rule metadata.
Condition that triggers the rule. If not specified, the rule is triggered for all recommendations.
Effect of the rule.
Description of the rule's purpose. This can be helpful for display in the Algolia dashboard.
"Boost on-sale items"
Indicates whether to enable the rule. If it isn't enabled, it isn't applied at query time.
Unique identifier of a rule object.
Time periods when the rule is active.
Response
OK
Response, taskID, and update timestamp.
Unique identifier of a task.
A successful API response means that a task was added to a queue.
It might not run immediately.
You can check the task's progress with the task operation and this task ID.
1514562690001
Date and time when the object was updated, in RFC 3339 format.
"2023-07-04T12:49:15Z"