-
Notifications
You must be signed in to change notification settings - Fork 29
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(specs): add recommend batch rules endpoint (generated)
algolia/api-clients-automation#3782 Co-authored-by: algolia-bot <accounts+algolia-api-client-bot@algolia.com> Co-authored-by: Raed <raed.chammam@algolia.com> Co-authored-by: Pierre Millot <pierre.millot@algolia.com> Co-authored-by: Clément Vannicatte <vannicattec@gmail.com>
- Loading branch information
1 parent
0ef99a5
commit 86ae17c
Showing
4 changed files
with
127 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
44 changes: 44 additions & 0 deletions
44
src/main/scala/algoliasearch/recommend/RecommendUpdatedAtResponse.scala
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
/** Recommend API The Recommend API lets you retrieve recommendations from one of Algolia's AI recommendation models | ||
* that you previously trained on your data. ## Client libraries Use Algolia's API clients and libraries to reliably | ||
* integrate Algolia's APIs with your apps. The official API clients are covered by Algolia's [Service Level | ||
* Agreement](https://www.algolia.com/policies/sla/). See: [Algolia's | ||
* ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/) ## Base URLs | ||
* The base URLs for requests to the Recommend API are: - `https://{APPLICATION_ID}.algolia.net` - | ||
* `https://{APPLICATION_ID}-dsn.algolia.net`. If your subscription includes a [Distributed Search | ||
* Network](https://dashboard.algolia.com/infra), this ensures that requests are sent to servers closest to users. Both | ||
* URLs provide high availability by distributing requests with load balancing. **All requests must use HTTPS.** ## | ||
* Retry strategy To guarantee a high availability, implement a retry strategy for all API requests using the URLs of | ||
* your servers as fallbacks: - `https://{APPLICATION_ID}-1.algolianet.com` - | ||
* `https://{APPLICATION_ID}-2.algolianet.com` - `https://{APPLICATION_ID}-3.algolianet.com` These URLs use a different | ||
* DNS provider than the primary URLs. You should randomize this list to ensure an even load across the three servers. | ||
* All Algolia API clients implement this retry strategy. ## Authentication To authenticate your API requests, add | ||
* these headers: - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. An API key with the | ||
* necessary permissions to make the request. The required access control list (ACL) to make a request is listed in | ||
* each endpoint's reference. You can find your application ID and API key in the [Algolia | ||
* dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must be JSON objects. ## | ||
* Response status and errors The Recommend API returns JSON responses. Since JSON doesn't guarantee any specific | ||
* ordering, don't rely on the order of attributes in the API response. Successful responses return a `2xx` status. | ||
* Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a `message` | ||
* property with more information. ## Version The current version of the Recommend API is version 1, as indicated by | ||
* the `/1/` in each endpoint's URL. | ||
* | ||
* The version of the OpenAPI document: 1.0.0 | ||
* | ||
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). | ||
* https://openapi-generator.tech Do not edit the class manually. | ||
*/ | ||
package algoliasearch.recommend | ||
|
||
/** Response, taskID, and update timestamp. | ||
* | ||
* @param taskID | ||
* 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](#tag/Indices/operation/getTask) and | ||
* this `taskID`. | ||
* @param updatedAt | ||
* Date and time when the object was updated, in RFC 3339 format. | ||
*/ | ||
case class RecommendUpdatedAtResponse( | ||
taskID: Long, | ||
updatedAt: String | ||
) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
/** Recommend API The Recommend API lets you retrieve recommendations from one of Algolia's AI recommendation models | ||
* that you previously trained on your data. ## Client libraries Use Algolia's API clients and libraries to reliably | ||
* integrate Algolia's APIs with your apps. The official API clients are covered by Algolia's [Service Level | ||
* Agreement](https://www.algolia.com/policies/sla/). See: [Algolia's | ||
* ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/) ## Base URLs | ||
* The base URLs for requests to the Recommend API are: - `https://{APPLICATION_ID}.algolia.net` - | ||
* `https://{APPLICATION_ID}-dsn.algolia.net`. If your subscription includes a [Distributed Search | ||
* Network](https://dashboard.algolia.com/infra), this ensures that requests are sent to servers closest to users. Both | ||
* URLs provide high availability by distributing requests with load balancing. **All requests must use HTTPS.** ## | ||
* Retry strategy To guarantee a high availability, implement a retry strategy for all API requests using the URLs of | ||
* your servers as fallbacks: - `https://{APPLICATION_ID}-1.algolianet.com` - | ||
* `https://{APPLICATION_ID}-2.algolianet.com` - `https://{APPLICATION_ID}-3.algolianet.com` These URLs use a different | ||
* DNS provider than the primary URLs. You should randomize this list to ensure an even load across the three servers. | ||
* All Algolia API clients implement this retry strategy. ## Authentication To authenticate your API requests, add | ||
* these headers: - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. An API key with the | ||
* necessary permissions to make the request. The required access control list (ACL) to make a request is listed in | ||
* each endpoint's reference. You can find your application ID and API key in the [Algolia | ||
* dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must be JSON objects. ## | ||
* Response status and errors The Recommend API returns JSON responses. Since JSON doesn't guarantee any specific | ||
* ordering, don't rely on the order of attributes in the API response. Successful responses return a `2xx` status. | ||
* Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a `message` | ||
* property with more information. ## Version The current version of the Recommend API is version 1, as indicated by | ||
* the `/1/` in each endpoint's URL. | ||
* | ||
* The version of the OpenAPI document: 1.0.0 | ||
* | ||
* NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). | ||
* https://openapi-generator.tech Do not edit the class manually. | ||
*/ | ||
package algoliasearch.recommend | ||
|
||
/** TimeRange | ||
* | ||
* @param from | ||
* When the rule should start to be active, in Unix epoch time. | ||
* @param until | ||
* When the rule should stop to be active, in Unix epoch time. | ||
*/ | ||
case class TimeRange( | ||
from: Int, | ||
until: Int | ||
) |