List the tasks of a job
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/tasks/v2-job-work-pipeline-index-for-job.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
GET/
Check success, not only the HTTP status: when the job's order is neither a draft nor published, this call answers HTTP 200 with { "status": 500, "success": false, "error": { "code": "action_not_allowed", "message": null } } instead of the list.
Returns every task of one job, with its preset, status, dates and assignees. Not paged.
Business rules
- The job's order must be a draft or published; otherwise the reply is HTTP 200 with
success: falseanderror.codeaction_not_allowed.
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The job's hash id (
id). Hash ids only: a unique key or a document number gives 404.- Example
WaGvtaWsx7Kcn4
- Example
Request body
This operation takes no request body.
Response
200Successful response.
Errors
401The API key is missing or wrong (
unauthenticated).403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- The job isn't on one of your team's orders, or its order was deleted.
- Fix
- Check the job id.
Notes
- A refusal here is HTTP 200 with
success: falseanderror.codeaction_not_allowed(the body'sstatussays 500). A client that only checks the HTTP status will treat it as done.
Related
- POSTAdd a task to a job
/v2/ api/ store/ {team_slug}/ v2/ job/ {hash_id}/ work_pipeline - GETGet a task
/v2/ api/ store/ {team_slug}/ v2/ work_pipeline/ {hash_id} - POSTFilter tasks
/v1/ api/ store/ {team_slug}/ work_pipeline/ filter
