# List the tasks of a job

```http
GET https://secure.yoprint.com/v2/api/store/{team_slug}/v2/job/{hash_id}/work_pipeline
```

- API version: v2
- Operation ID: `v2_public_job_work_pipeline_index_for_job`
- Section: Production › [Tasks](https://developer.yoprint.com/reference/tasks.md)
- Web page: https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-index-for-job/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

**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.

## Permission

Any member of the team. No sales order permission is checked.

## Business rules

- The job's order must be a draft or published; otherwise the reply is HTTP 200 with `success: false` and `error.code` `action_not_allowed`.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The job's hash id (`id`). Hash ids only: a unique key or a document number gives 404. Example `WaGvtaWsx7Kcn4`.

## Request body

This operation takes no request body.

### Example request

```bash
curl 'https://secure.yoprint.com/v2/api/store/your-team/v2/job/WaGvtaWsx7Kcn4/work_pipeline' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

> **Warning: a 200 answer can still be a refusal.** Check `success` (and the fields named below) as well as the HTTP status.
> - The order is in a state this call refuses: `success: false`, `error.code` `action_not_allowed`. Fix: Check `success` in every reply. Publish the order (or work on a draft) first.

Refusal example (Refused with HTTP 200: `success` is false):

```json
{
  "error": {
    "code": "action_not_allowed",
    "message": null
  },
  "status": 500,
  "success": false
}
```

Example response:

```json
{
  "data": [
    {
      "assigned_users": [
        {
          "avatar_url": null,
          "id": "4mdDkMg3dgQOa3",
          "name": "Alex Rivera"
        }
      ],
      "created_at": "2026-11-03T15:00:00+00:00",
      "due_date": "2026-11-05T17:00:00+00:00",
      "id": "hpioY1gDBQZdbI",
      "job_id": "WaGvtaWsx7Kcn4",
      "job_is_rush": 1,
      "job_item_count": 48,
      "job_name": "Front print",
      "job_scoped_id": "JOB-2419",
      "job_status_id": "scaWHQnPLtqMPT",
      "name": "Burn screens",
      "note": null,
      "order_id": "sFbALVSYD55eXe",
      "order_name": "Team shirts",
      "order_scoped_id": "SO1001",
      "pipeline_id": "SE3SfXjt6dPfnH",
      "position": 1,
      "sales_order": {
        "customer_id": "ifAHmADekGZ6id",
        "customer_name": "Northwind Apparel",
        "is_quote": false,
        "object_type": "sales_order",
        "status_id": "wgbOT87gGZvhgy"
      },
      "start_date": "2026-11-04T09:00:00+00:00",
      "status": {
        "color": "#2196f3",
        "customer_label": "In Progress",
        "id": "hTFITko5Q0R83y",
        "label": "Burning",
        "pipeline_id": "SE3SfXjt6dPfnH",
        "position": 2,
        "role": "pipeline",
        "trashed": false,
        "type": "in_progress"
      },
      "status_completion_date": null,
      "status_id": "hTFITko5Q0R83y",
      "status_last_change_date": "2026-11-03T15:05:00+00:00",
      "updated_at": "2026-11-03T15:05:00+00:00"
    }
  ],
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
- `403` You 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, with `unauthorized` or `user_is_not_authorized`.
- `404` Not 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: false` and `error.code` `action_not_allowed` (the body's `status` says 500). A client that only checks the HTTP status will treat it as done.

## Related

- [Add a task to a job](https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-store.md): `POST /v2/api/store/{team_slug}/v2/job/{hash_id}/work_pipeline`
- [Get a task](https://developer.yoprint.com/reference/tasks/v2-job-work-pipeline-show.md): `GET /v2/api/store/{team_slug}/v2/work_pipeline/{hash_id}`
- [Filter tasks](https://developer.yoprint.com/reference/tasks/v1-work-pipeline-filter.md): `POST /v1/api/store/{team_slug}/work_pipeline/filter`