CFs submitted against a task, in Merkle Layer-1 order
An unknown task is a **404**; a known task with no CFs is a 200 with an empty page — the two are deliberately distinguished, unlike `/datasets/{id}/cfs`. See `TaskCfsPage` for the two properties that matter to a consumer building a dataset: the ordering guarantee, and the fact that this is a live listing rather than a snapshot.
v1/tasks/{id}/cfsPath Parameters
idRequiredstring
The task's 32-byte id.
"^0[xX][0-9a-fA-F]{64}$"Query Parameters
limitinteger
Page size. Server-configured default and ceiling (API_DEFAULT_LIMIT /
API_MAX_LIMIT; 50 and 200 unless overridden). A value above the ceiling
is silently clamped, not rejected — check pagination.limit in the
response rather than assuming the requested value was honoured. Values
below 1, or non-integers, are a 400.
1cursorstring
Opaque cursor from a previous response's pagination.nextCursor. Omit
for the first page. A malformed cursor is a 400.
A page of the task's current CF set.
Last updated