curl --request POST \
  --url https://api.arize.com/v2/tasks/{task_id}/trigger \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "data_start_time": "2026-03-01T00:00:00Z",
  "data_end_time": "2026-03-07T00:00:00Z",
  "max_spans": 5000,
  "override_evaluations": false
}
'

{
  "id": "VGFza1J1bjo5OTpxUndY",
  "task_id": "T25saW5lVGFzazo0NTpxUndY",
  "status": "pending",
  "run_started_at": null,
  "run_finished_at": null,
  "data_start_time": "2026-03-01T00:00:00.000Z",
  "data_end_time": "2026-03-07T00:00:00.000Z",
  "num_successes": 0,
  "num_errors": 0,
  "num_skipped": 0,
  "created_at": "2026-03-07T10:30:00.000Z",
  "created_by_user_id": "VXNlcjoxOm5OYkM="
}

Tasks

Trigger a task run

Triggers a new run on an existing task. The run is queued and processed asynchronously. Poll GET /v2/task-runs/{run_id} until the run reaches a terminal status (completed, failed, or cancelled).

Payload Requirements

Fields must match the task’s type; sending inapplicable fields returns 400.
For template_evaluation / code_evaluation tasks, all trigger fields are optional — an empty body uses server defaults.
For run_experiment tasks, experiment_name is required.

For run_experiment tasks

Supply experiment_name (required) plus any of the optional per-run fields: dataset_version_id, example_ids (exclusive with max_examples), max_examples, tracing_metadata, evaluation_task_ids.

The fields data_start_time, data_end_time, max_spans, override_evaluations, and experiment_ids are not applicable and will return 400 if supplied.

The response includes experiment_id once the experiment is provisioned.

For template_evaluation / code_evaluation tasks

Supply data_start_time, data_end_time, max_spans, override_evaluations, and/or experiment_ids as needed. run_experiment-specific fields are not applicable for these task types.

Valid example (trigger a run_experiment run)

{
  "experiment_name": "GPT-4o Baseline v2",
  "max_examples": 50
}

Invalid example (run_experiment trigger missing required experiment_name)

{
  "max_examples": 50
}

This endpoint is in alpha, read more here.

POST

tasks

{task_id}

trigger

curl --request POST \
  --url https://api.arize.com/v2/tasks/{task_id}/trigger \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "data_start_time": "2026-03-01T00:00:00Z",
  "data_end_time": "2026-03-07T00:00:00Z",
  "max_spans": 5000,
  "override_evaluations": false
}
'

{
  "id": "VGFza1J1bjo5OTpxUndY",
  "task_id": "T25saW5lVGFzazo0NTpxUndY",
  "status": "pending",
  "run_started_at": null,
  "run_finished_at": null,
  "data_start_time": "2026-03-01T00:00:00.000Z",
  "data_end_time": "2026-03-07T00:00:00.000Z",
  "num_successes": 0,
  "num_errors": 0,
  "num_skipped": 0,
  "created_at": "2026-03-07T10:30:00.000Z",
  "created_by_user_id": "VXNlcjoxOm5OYkM="
}

Authorizations

Authorization

string

header

required

Most Arize AI endpoints require authentication. For those endpoints that require authentication, include your API key in the request header using the format

Path Parameters

task_id

string

required

The unique task identifier (base64) A universally unique identifier (base64-encoded opaque string).

Example:

"RW50aXR5OjEyMzQ1"

Body

application/json

Trigger body for POST /v2/tasks/{task_id}/trigger. The server derives the task type from the URL's task record and selects the appropriate schema; the body itself does not carry a task_type field.

Task type	Schema
`template_evaluation`	`TriggerEvaluationTaskRunRequest`
`code_evaluation`	`TriggerEvaluationTaskRunRequest`
`run_experiment`	`TriggerRunExperimentTaskRunRequest`

Sending a field that is not valid for the resolved task type returns 400. For template_evaluation and code_evaluation tasks all trigger fields are optional — an empty body is valid and uses server defaults.

Option 1
Option 2

Trigger request for template_evaluation or code_evaluation tasks. data_start_time and data_end_time together must span no more than 30 days. data_start_time must be before data_end_time.

data_start_time

string<date-time>

ISO 8601 start of the data window to evaluate. For model-based tasks, defaults to the task's last run time. Required on the first run (when no previous run exists). Not applicable to dataset-based tasks.

data_end_time

string<date-time>

ISO 8601 end of the data window to evaluate. For model-based tasks, defaults to now. Not applicable to dataset-based tasks.

max_spans

integer

Maximum number of spans to process (default 10000).

Required range: x >= 1

override_evaluations

boolean

Whether to re-evaluate data that already has evaluation labels (default false).

experiment_ids

string[]

Experiment identifiers (base64) to run against. Only for dataset-based template_evaluation / code_evaluation tasks.

Response

Returns the created task run

A task run is an async job that executes the work defined on a task. Runs are created by triggering an existing task (POST /v2/tasks/{task_id}/trigger). For run_experiment tasks, experiment_id is populated after the experiment is provisioned; poll GET /v2/task-runs/{run_id} until status reaches a terminal state.

string

required

The unique identifier for the task run.

task_id

string

required

The parent task identifier (base64).

status

enum<string>

required

Status of a task run.

pending - The run has been created but not yet started.
running - The run is currently in progress.
completed - The run finished successfully.
failed - The run encountered an error and stopped.
cancelled - The run was cancelled before completion.

Available options:

pending,

running,

completed,

failed,

cancelled

run_started_at

string<date-time> | null

required

When the run started processing.

run_finished_at

string<date-time> | null

required

When the run finished processing.

data_start_time

string<date-time> | null

required

Start of the data window evaluated. Null for run_experiment runs.

data_end_time

string<date-time> | null

required

End of the data window evaluated. Null for run_experiment runs.

num_successes

integer

required

Number of successfully evaluated items.

num_errors

integer

required

Number of items that errored during evaluation.

num_skipped

integer

required

Number of items that were skipped.

created_at

string<date-time>

required

When the run was created.

created_by_user_id

string | null

required

The unique identifier for the user who triggered the run.

experiment_id

string | null

Created experiment identifier (base64). Present only for run_experiment task runs; null for all other task types.

List task runs Get task run

⌘I