Create a new trajectory for a workflow.
The workflow must exist and belong to the authenticated organization. The trajectory_data must contain at least one item.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Unique key for idempotent requests. If provided, the server ensures the request is processed at most once. Retries with the same key return the original response. SDKs auto-generate this for write requests.
"550e8400-e29b-41d4-a716-446655440000"
Schema for creating a trajectory.
Note: is_generated is intentionally omitted here. New trajectories always
start as non-generated and must be promoted via
POST /runs/{run_id}/generate-trajectory.
1Display dimensions when trajectory was recorded
255Optional run that created this trajectory
Original input values used when trajectory was created
Whether this trajectory is approved for use
Successful Response
Trajectory response schema
1Display dimensions when trajectory was recorded
255Optional run that created this trajectory
Original input values used when trajectory was created