# List tasks in a date range

```http
POST https://secure.yoprint.com/v1/api/store/{team_slug}/work_pipeline/calendar
```

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

Tasks whose start or due date falls in the range, or whose dates span it. Returns at most 1,200 Tasks, in the requested sort, then Task id order. This route ignores `page` and `per_page` and never returns `pagination`.

The range runs from the start of the day of `start_date` to the end of the day of `end_date`. Send both as ISO 8601 date-times in UTC (`2026-11-01T00:00:00Z`): the day boundaries are taken from the date as written. Only tasks of live jobs on sales orders are listed.

If a range may hold more than 1,200 tasks, split it into shorter ranges. You can narrow it with the same `filters` and `sort` as Filter tasks. A date filter's `value` is a whole number of days, counted from the moment of the request in UTC: `eq` N matches the whole UTC day N days from today (0 is today, -1 yesterday); `gte` N matches dates on or after now plus N days; `lte` N matches dates on or before now **minus** N days. So "due in the next 7 days" is `due_date gte 0` and `due_date lte -7`, and "overdue" is `due_date lte 0`. This differs from the v2 filters (Filter invoices, the production control calendar), where `lte` and `gte` both count forward.

## Permission

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

## Business rules

- `start_date` and `end_date` are required ISO 8601 dates.
- A task is in the range when its start or due date falls in it, or it starts before and is due after it. Undated tasks never appear.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.

## Request body

Content type `application/json`, required.

Fields:

- `end_date` (string (date-time), required): The last day of the range (ISO 8601).
- `start_date` (string (date-time), required): The first day of the range (ISO 8601).
- `filters` (array of objects, optional): Conditions, all of which must match. Omit for no filter. At least 1 item.
  - Each item:
    - `key` (string, required): What to filter on. See the table in the description. One of: `"status_id"`, `"status_type"`, `"pipeline_id"`, `"assigned_users"`, `"assigned_to_me"`, `"order_created_by"`, `"is_rush"`, `"start_date"`, `"due_date"`, `"start_date_is_set"`, `"due_date_is_set"`, `"status_last_change_date"`, `"status_completion_date"`, `"search"`.
    - `operator` (string, required): How to compare. Each kind of key accepts only some operators. One of: `"eq"`, `"neq"`, `"gt"`, `"gte"`, `"lt"`, `"lte"`, `"in"`, `"nin"`, `"bt"`, `"ct"`, `"sw"`, `"ew"`.
    - `value` (string | number | boolean | array, required): What to compare with: text, a number of days, true or false, or an array of hash ids or options, by kind of key.
- `sort` (array of objects, optional): Sort keys, applied in order, then by task id. Without `sort` the tasks come by task id.
  - Each item:
    - `direction` (string, required): One of: `"asc"`, `"desc"`.
    - `key` (string, required): One of: `"status_id"`, `"status_label"`, `"pipeline_id"`, `"job_id"`, `"start_date"`, `"due_date"`, `"status_last_change_date"`, `"status_completion_date"`, `"job_item_count"`, `"order_cust_due_date"`, `"order_due_date"`, `"order_ship_due_date"`, `"order_ship_due_date_undated_last"`, `"created_at_id"`.

### Example request

```bash
curl -X POST 'https://secure.yoprint.com/v1/api/store/your-team/work_pipeline/calendar' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1' \
  -H 'Content-Type: application/json' \
  -d '{
    "end_date": "2026-11-07T00:00:00Z",
    "filters": [
      {
        "key": "pipeline_id",
        "operator": "in",
        "value": [
          "SE3SfXjt6dPfnH"
        ]
      }
    ],
    "start_date": "2026-11-01T00:00:00Z"
  }'
```

## Response

`200` Successful response.

Fields:

- `data` (array of objects, required)
  - Each item:
    - `assigned_users` (array of objects, optional): Who is assigned.
      - Each item:
        - `avatar_url` (string | null, optional)
        - `id` (string, optional): The user.
        - `name` (string, optional)
    - `created_at` (string (date-time), optional)
    - `due_date` (string (date-time) | null, optional): Task due date. ISO 8601 with offset, or null.
    - `id` (string, optional): The task.
    - `job_id` (string, optional): The job.
    - `job_is_rush` (boolean | integer | null, optional)
    - `job_item_count` (number | null, optional)
    - `job_name` (string | null, optional)
    - `job_scoped_id` (string, optional): The job number with its prefix.
    - `job_status_id` (string | null, optional): The job's current status.
    - `name` (string, optional)
    - `note` (string | null, optional)
    - `order_id` (string, optional): The order.
    - `order_name` (string | null, optional)
    - `order_scoped_id` (string | null, optional): The order number.
    - `pipeline_id` (string, optional): The task preset it comes from.
    - `position` (integer, optional): Order among tasks; lower comes first. 0 when unset.
    - `sales_order` (object, optional): A summary of the job's order.
      - `created_by` (string | null, optional): Who created the order.
      - `cust_due_date` (string (date-time) | null, optional): Order customer due (in-hand) date. ISO 8601 with offset, or null.
      - `customer_id` (string | null, optional): The customer.
      - `customer_name` (string | null, optional)
      - `due_date` (string (date-time) | null, optional): Order production due date. ISO 8601 with offset, or null.
      - `external_type` (string | null, optional): `shopify` when the order came from Shopify, else null.
      - `is_quote` (boolean, optional)
      - `issue_date` (string (date-time) | null, optional): Order issue date. ISO 8601 with offset, or null.
      - `object_type` (string | null, optional): `sales_order` or `quote`.
      - `ship_due_date` (string (date-time) | null, optional): Order ship-by date. ISO 8601 with offset, or null.
      - `shopify_deleted_externally` (boolean, optional)
      - `shopify_deleted_externally_at` (string (date-time) | null, optional): When it was deleted in Shopify. ISO 8601 with offset, or null.
      - `start_date` (string (date-time) | null, optional): Order production start. ISO 8601 with offset, or null.
      - `status_id` (string | null, optional): The order status.
    - `start_date` (string (date-time) | null, optional): Task start. ISO 8601 with offset, or null.
    - `status` (object, optional): A status: label, kind and place in the list.
      - `color` (string | null, optional): Hex color.
      - `customer_label` (string, optional)
      - `id` (string, optional): The status.
      - `label` (string, optional)
      - `pipeline_id` (string, optional): Only on the statuses of a task preset (`role` `pipeline`): the task preset. Absent on other statuses.
      - `position` (integer, optional): Its place in the team's list: sort by it to find the next status.
      - `role` (string, optional): Which list it belongs to: `job` for job statuses, `pipeline` for the statuses of a task preset. One of: `"order"`, `"quote"`, `"job"`, `"purchase_order"`, `"shipment"`, `"customer_message"`, `"pipeline"`.
      - `trashed` (boolean, optional): The status was deleted.
      - `type` (string, optional): The kind of status: `start` (Pending), `pre_production` and `in_progress` (In Progress), `end` (Completed). One of: `"start"`, `"pre_production"`, `"in_progress"`, `"end"`.
    - `status_completion_date` (string (date-time) | null, optional): When it reached a Completed status. ISO 8601 with offset, or null.
    - `status_id` (string, optional): The task's status (a status of its task preset).
    - `status_last_change_date` (string (date-time) | null, optional): When the status last changed. ISO 8601 with offset, or null.
    - `updated_at` (string (date-time), optional)
- `status` (integer, required)
- `success` (boolean, required)

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.
- `422` The request was refused and changed nothing. `validation_failed` lists what to fix in `error.fields`; other codes name a business rule, explained in `error.message`. A few checks answer with only `{"message": "..."}`. An operation that calls another service (a payment provider, a carrier, an accounting app) can answer `connect_timeout` ("Please retry again") when that service does not answer in time: the change may or may not have happened there, so read the record back before you retry.
  - When: A date is missing or not ISO 8601, or a filter is invalid. Fix: Send both dates and valid filters.

## Notes

- You get the 1,200 tasks with the lowest ids (or first in your sort) in the range; nothing tells you more were left out.

## Related

- [Filter tasks](https://developer.yoprint.com/reference/tasks/v1-work-pipeline-filter.md): `POST /v1/api/store/{team_slug}/work_pipeline/filter`
- [List jobs in a date range](https://developer.yoprint.com/reference/jobs/v1-job-calendar.md): `POST /v1/api/store/{team_slug}/job/calendar`
- [Read the production control calendar](https://developer.yoprint.com/reference/production-control/v1-production-control-filter.md): `POST /v1/api/store/{team_slug}/production_control/filter`