POST /1/transformations/{transformationID}/try

Try a transformation before updating it.

Servers

https://data.{region}.algolia.com

Path parameters

Name	Type	Required	Description
`transformationID`	String	Yes	Unique identifier of a transformation.

Request headers

Name	Type	Required	Description
`Content-Type`	String	Yes	The media type of the request body. Default value: "application/json"

Request body fields

Name	Type	Required	Description
`input`		No	The input for the transformation, which can be either code or a no-code configuration.
`authentications[]`	Array	No
`authentications[].name`	String	Yes	Descriptive name for the resource.
`authentications[].input`		Yes
`authentications[].platform`		No
`authentications[].type`	String	Yes	Type of authentication. This determines the type of credentials required in the `input` object. Possible values: `"googleServiceAccount"` `"apiKey"` `"oauth"` `"algoliaInsights"` `"algolia"` `"secrets"` `"basic"`
`type`	String	No	The type of transformation, which can be either 'code' or 'noCode'. Possible values: `"noCode"` `"code"`
`sampleRecord`	Object	Yes	The record to apply the given code to.
`code`	String	No	It is deprecated. Use the `input` field with proper `type` instead to specify the transformation code.

How to start integrating

Add HTTP Task to your workflow definition.
Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
Click Test request to test run your request to the API and see the API's response.