---
title: "Get all tasks"
method: GET
path: "/tasks"
tags: ["Tasks"]
---

# Get all tasks

`GET /tasks`

Get information as a list of all tasks.

## Query parameters

- `count` integer
- `offset` integer
- `sort_field` string
- `sort_direction` 'ASC' | 'DESC'
- `task_type_id` string
- `task_state_id` string
- `customer_id` string
- `priority` 1 | 2 | 3 | 4
- `due_date` string
- `task_title` string
- `task_note` string

## Headers

- `Accept-Language` string

## Response `200`

OK

- object
  - `data` object
    - `tasks` Task[] — List of all tasks.
      - `task_id` string — The unique ID of the task.
      - `task_type_id` string, required — The unique ID of the task type. [GET /task-types](https://carecloud.readme.io/reference/gettasktypes)
      - `task_state_id` string, required — The unique ID of the task state. [GET /task-states](https://carecloud.readme.io/reference/gettaskstates)
      - `customer_id` string, required — The unique ID of the customer. [GET /customers](https://carecloud.readme.io/reference/getcustomers)
      - `task_note` string — Text note of the task.
      - `task_title` string, required — Title of the task.
      - `task_priority` 1 | 2 | 3 | 4, required — The parameter filters tasks by their priority. *Possible values are: 1 - Critical / 2 - Major / 3 - Normal / 4 - Minor.*
      - `due_date` string, date — Due date of the task in ISO-8601 format (`YYYY-MM-DD`).
      - `created_at` string — Timestamp of the task creation. Format: `YYYY-MM-DD HH:MM:SS`. All times are in the local timezone.
      - `state` 0 | 1 | 2 — State of the task. *Possible values are: 0 - deleted / 1 - active / 2 - non active*
    - `total_items` integer — The number of all found tasks.

## Other responses

- `400` — Bad input parameter. The response body's `error.error_data.invalid_params[]` array lists the parameters that caused the failure, each carrying a `reason` code. See the `BadRequestErrorBody` schema for the generic reason taxonomy. Operations with domain-specific business rules document additional reasons at the operation level.
- `401` — The client has invalid credentials or auth token.
- `403` — The client does not exist or the client tried to access an unauthorized property or resource.
- `404` — The resource was not found.
- `405` — The resource does not support the specified HTTP method.
- `429` — Too many requests - more than the resource limit.
- `500` — Server is not working as expected.
- `503` — Temporary state when the service is temporarily unavailable, overloaded or there is a maintenance window.

---

[API](https://skmtc.net/crmcarecloud/apis/rest-api-reference.md) · [All operations](https://skmtc.net/crmcarecloud/apis/rest-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/crmcarecloud/rest-api-reference/versions/329c06dbf8d9/schema)