Get job events
The ordered lifecycle of one job: queued, provider_submitted, provider_completed, settled, failed, canceled, webhook_delivered, webhook_failed. The engine appends these while the job runs. A job that ran before the timeline existed falls back to the steps its own row timestamps can prove, and therefore shows no webhook events.
The ordered lifecycle of one job: queued, provider_submitted, provider_completed, settled, failed, canceled, webhook_delivered, webhook_failed. The engine appends these while the job runs. A job that ran before the timeline existed falls back to the steps its own row timestamps can prove, and therefore shows no webhook events.
Authorization
bearerAuth API key authentication. Use your API key as the bearer token: Authorization: Bearer roasos_sk_...
In: header
Path Parameters
uuidResponse Body
application/json
application/json
application/json
curl -X GET "https://example.com/v1/jobs/497f6eca-6276-4993-bfeb-53cbbbba6f08/events"{ "data": [ { "seq": 0, "event": "queued", "at": "string" } ]}Get a job result
The result of a completed job. A job that is still running answers 409 run_not_completed.
Cancel a job
Cancel a job that has not finished. The engine reads the cancellation immediately before it submits the request to the model provider. When the job has not been submitted, the run stops, the whole credit reservation is refunded, the job becomes canceled, and the response returns cancel_honoured: true. When the provider already holds the request it cannot be recalled: the cancellation is recorded, the run finishes, the job is billed normally, and the response returns cancel_honoured: false. A job that already finished answers 409 job_not_cancelable.