|
| 1 | +/** Recommend API The Recommend API lets you retrieve recommendations from one of Algolia's AI recommendation models |
| 2 | + * that you previously trained on your data. ## Client libraries Use Algolia's API clients and libraries to reliably |
| 3 | + * integrate Algolia's APIs with your apps. The official API clients are covered by Algolia's [Service Level |
| 4 | + * Agreement](https://www.algolia.com/policies/sla/). See: [Algolia's |
| 5 | + * ecosystem](https://www.algolia.com/doc/guides/getting-started/how-algolia-works/in-depth/ecosystem/) ## Base URLs |
| 6 | + * The base URLs for requests to the Recommend API are: - `https://{APPLICATION_ID}.algolia.net` - |
| 7 | + * `https://{APPLICATION_ID}-dsn.algolia.net`. If your subscription includes a [Distributed Search |
| 8 | + * Network](https://dashboard.algolia.com/infra), this ensures that requests are sent to servers closest to users. Both |
| 9 | + * URLs provide high availability by distributing requests with load balancing. **All requests must use HTTPS.** ## |
| 10 | + * Retry strategy To guarantee a high availability, implement a retry strategy for all API requests using the URLs of |
| 11 | + * your servers as fallbacks: - `https://{APPLICATION_ID}-1.algolianet.com` - |
| 12 | + * `https://{APPLICATION_ID}-2.algolianet.com` - `https://{APPLICATION_ID}-3.algolianet.com` These URLs use a different |
| 13 | + * DNS provider than the primary URLs. You should randomize this list to ensure an even load across the three servers. |
| 14 | + * All Algolia API clients implement this retry strategy. ## Authentication To authenticate your API requests, add |
| 15 | + * these headers: - `x-algolia-application-id`. Your Algolia application ID. - `x-algolia-api-key`. An API key with the |
| 16 | + * necessary permissions to make the request. The required access control list (ACL) to make a request is listed in |
| 17 | + * each endpoint's reference. You can find your application ID and API key in the [Algolia |
| 18 | + * dashboard](https://dashboard.algolia.com/account). ## Request format Request bodies must be JSON objects. ## |
| 19 | + * Response status and errors The Recommend API returns JSON responses. Since JSON doesn't guarantee any specific |
| 20 | + * ordering, don't rely on the order of attributes in the API response. Successful responses return a `2xx` status. |
| 21 | + * Client errors return a `4xx` status. Server errors are indicated by a `5xx` status. Error responses have a `message` |
| 22 | + * property with more information. ## Version The current version of the Recommend API is version 1, as indicated by |
| 23 | + * the `/1/` in each endpoint's URL. |
| 24 | + * |
| 25 | + * The version of the OpenAPI document: 1.0.0 |
| 26 | + * |
| 27 | + * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). |
| 28 | + * https://openapi-generator.tech Do not edit the class manually. |
| 29 | + */ |
| 30 | +package algoliasearch.recommend |
| 31 | + |
| 32 | +/** Response, taskID, and update timestamp. |
| 33 | + * |
| 34 | + * @param taskID |
| 35 | + * Unique identifier of a task. A successful API response means that a task was added to a queue. It might not run |
| 36 | + * immediately. You can check the task's progress with the [`task` operation](#tag/Indices/operation/getTask) and |
| 37 | + * this `taskID`. |
| 38 | + * @param updatedAt |
| 39 | + * Date and time when the object was updated, in RFC 3339 format. |
| 40 | + */ |
| 41 | +case class RecommendUpdatedAtResponse( |
| 42 | + taskID: Long, |
| 43 | + updatedAt: String |
| 44 | +) |
0 commit comments