Skip to main content
GET
查询运行

端点

认证:需要 API Key(Authorization: Bearer <API Key>)。 状态、进度、错误对象、上游任务引用、用量与费用。wait 大于 0 时服务端保持连接直到运行到终态或超时,仍未到终态就原样再调一次,不要用 wait=0 高频轮询。 只能读自己发起的运行:别人的 run_id 和不存在的 run_id 都返回 404。输入契约中标记 sensitive 的字段在回显里被打码,明文只写不读,发起人也读不回。

请求

路径参数

string
必填
运行标识。

查询参数

number
默认值:"0"
长轮询秒数,0-60,默认 0 立即返回。范围 0 到 60。

示例请求

响应

200 成功

字段与发起运行的返回相同。 响应包在 data 字段中,其内容如下。
string
必填
—
string
—
string
—
string
—
string
—
string
—
enum
必填
取值:PENDING / QUEUED / RUNNING / SUCCEEDED / PARTIALLY_SUCCEEDED / FAILED / CANCELLED / EXPIRED。
object
—
object
—
string
—
boolean
—
boolean
true while cancellation has been requested and the run is still winding down (cooperative stop / partial-result recovery); always false in terminal states (normalized server-side), so consumers need not derive it from state
string
—
string
—
string
—
string
—
string
when the run was first claimed by a worker. Unlike started_at, which is re-stamped on every retry, this one is never rewritten, so it is the anchor for queue time: queued = first_started_at - created_at, and total wall time = finished_at - first_started_at. Deriving queue time from started_at counts the earlier attempts’ execution as queueing. Null only for runs never claimed.
string
—
object
Objective usage metering: how much the run did (kept separate from Billing; this is what evaluations compare against).
object
Billing ledger = Usage x pricing x billing_rules: how much is charged.
object
—
object[]
—
object[]
—

错误

错误响应统一为 {"error": {code, category, message, retryable}},见错误。

客户端库