feat(specs): add generate code endpoint to ingestion specs (generated)

algolia/api-clients-automation#3489

Co-authored-by: algolia-bot <[email protected]>
Co-authored-by: Clément Vannicatte <[email protected]>

Author: algolia-bot

src/main/scala/algoliasearch/api/IngestionClient.scala

@@ -27,6 +27,8 @@ import algoliasearch.ingestion.Event
 import algoliasearch.ingestion.EventSortKeys._
 import algoliasearch.ingestion.EventStatus._
 import algoliasearch.ingestion.EventType._
+import algoliasearch.ingestion.GenerateTransformationCodePayload
+import algoliasearch.ingestion.GenerateTransformationCodeResponse
 import algoliasearch.ingestion.ListAuthenticationsResponse
 import algoliasearch.ingestion.ListDestinationsResponse
 import algoliasearch.ingestion.ListEventsResponse
@@ -580,6 +582,31 @@ class IngestionClient(
     execute[TaskUpdateResponse](request, requestOptions)
   }
 
+  /** Generates code for the selected model based on the given prompt.
+    *
+    * Required API Key ACLs:
+    *   - addObject
+    *   - deleteIndex
+    *   - editSettings
+    */
+  def generateTransformationCode(
+      generateTransformationCodePayload: GenerateTransformationCodePayload,
+      requestOptions: Option[RequestOptions] = None
+  )(implicit ec: ExecutionContext): Future[GenerateTransformationCodeResponse] = Future {
+    requireNotNull(
+      generateTransformationCodePayload,
+      "Parameter `generateTransformationCodePayload` is required when calling `generateTransformationCode`."
+    )
+
+    val request = HttpRequest
+      .builder()
+      .withMethod("POST")
+      .withPath(s"/1/transformations/models")
+      .withBody(generateTransformationCodePayload)
+      .build()
+    execute[GenerateTransformationCodeResponse](request, requestOptions)
+  }
+
   /** Retrieves an authentication resource by its ID.
     *
     * Required API Key ACLs:
@@ -1134,7 +1161,7 @@ class IngestionClient(
     val request = HttpRequest
       .builder()
       .withMethod("GET")
-      .withPath(s"/1/transformations/copilot")
+      .withPath(s"/1/transformations/models")
       .build()
     execute[TransformationModels](request, requestOptions)
   }

src/main/scala/algoliasearch/ingestion/GenerateTransformationCodePayload.scala

@@ -0,0 +1,32 @@
+/** Ingestion API The Ingestion API lets you connect third-party services and platforms with Algolia and schedule tasks
+  * to ingest your data. The Ingestion API powers the no-code [data
+  * connectors](https://dashboard.algolia.com/connectors). ## Base URLs The base URLs for requests to the Ingestion API
+  * are: - `https://data.us.algolia.com` - `https://data.eu.algolia.com` Use the URL that matches your [analytics
+  * region](https://dashboard.algolia.com/account/infrastructure/analytics). **All requests must use HTTPS.** ##
+  * 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 Response bodies are JSON objects. Deleting a user token returns an
+  * empty response body with rate-limiting information as headers. 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. The Insights API doesn't validate if the event parameters such as `indexName`,
+  * `objectIDs`, or `userToken`, correspond to anything in the Search API. It justs checks if they're formatted
+  * correctly. Check the [Events](https://dashboard.algolia.com/events/health) health section, whether your events can
+  * be used for Algolia features such as Analytics, or Dynamic Re-Ranking. ## Version The current version of the
+  * Insights 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.ingestion
+
+/** GenerateTransformationCodePayload
+  */
+case class GenerateTransformationCodePayload(
+    id: String,
+    systemPrompt: Option[String] = scala.None,
+    userPrompt: String
+)

src/main/scala/algoliasearch/ingestion/GenerateTransformationCodeResponse.scala

@@ -0,0 +1,30 @@
+/** Ingestion API The Ingestion API lets you connect third-party services and platforms with Algolia and schedule tasks
+  * to ingest your data. The Ingestion API powers the no-code [data
+  * connectors](https://dashboard.algolia.com/connectors). ## Base URLs The base URLs for requests to the Ingestion API
+  * are: - `https://data.us.algolia.com` - `https://data.eu.algolia.com` Use the URL that matches your [analytics
+  * region](https://dashboard.algolia.com/account/infrastructure/analytics). **All requests must use HTTPS.** ##
+  * 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 Response bodies are JSON objects. Deleting a user token returns an
+  * empty response body with rate-limiting information as headers. 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. The Insights API doesn't validate if the event parameters such as `indexName`,
+  * `objectIDs`, or `userToken`, correspond to anything in the Search API. It justs checks if they're formatted
+  * correctly. Check the [Events](https://dashboard.algolia.com/events/health) health section, whether your events can
+  * be used for Algolia features such as Analytics, or Dynamic Re-Ranking. ## Version The current version of the
+  * Insights 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.ingestion
+
+/** GenerateTransformationCodeResponse
+  */
+case class GenerateTransformationCodeResponse(
+    generatedCode: Option[String] = scala.None
+)