OptionallabelOptional label for this execution when using applicationId. This label can be used to identify or categorize the execution. Note: This field is only applicable when applicationId is provided.
OptionalmessagesAn array of previous messages in the conversation. Each message should have a 'role' (e.g., 'user', 'assistant') and 'content'.
OptionaloverrideOverride default settings specified in the canvas. This allows for fine-tuning the completion behavior for this specific request.
Optionalfunctions?: {An array of functions that the model can call. This allows for more structured and interactive completions.
Optionalmodel?: stringThe specific model to use for this completion. If not specified, the default model set in the canvas will be used.
Optionaltemperature?: numberControls randomness in the output. Values between 0 and 1. Lower values make the output more focused and deterministic.
Specifies whether to use a chat or completion model.
OptionalpollingTime (in milliseconds if number) between polling attempts (e.g. "1s", "1m", "1h", "1d"). Controls how frequently the SDK checks batch completion status.
OptionalpollingMaximum time (in milliseconds if number) to wait for completion before timing out (e.g. "1s", "1m", "1h", "1d"). After timeout, polling stops but the batch continues processing on the server.
OptionaltagsOptional array of tags to associate with this execution. Tags can be used for filtering, categorization, and analytics.
OptionalwebhookWebhook configuration for batch completion notifications. Supports both URL and custom headers to forward.
OptionalwebhookOptional webhook URL to receive completion notifications. The server will POST to this URL when the batch completes, fails, or is canceled.
Configuration options for batch execution.
Batch executions are always asynchronous and return results via output file. Unlike single executions, batches do not support streaming or synchronous modes.