# List Tasks

Returns list of tasks. The list can be filtered with the , , or  query parameters. It can also be paginated with the  and  query parameters.

Endpoint: GET /v1/tasks
Version: 1.0
Security: serverToken

## Query parameters:

  - `name` (string)
    Task Name Filter. Filter by task name

  - `type` (string)
    Task Type Filter. Filter by task type

  - `state` (string)
    Task State Filter. Filter by task state
    Enum: "pending", "running", "failed", "completed"

  - `page` (integer)
    Page number for pagination

  - `size` (integer)
    Page size for pagination
    Example: 42

## Response 200 fields (application/json):

  - `id` (string)
    Example: "354b6adc10bc417eb715a8e7b21d6031"

  - `name` (string)

  - `type` (string)

  - `priority` (integer)

  - `data` (object)

  - `availableTime` (string)
    [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) / [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp _with_ timezone information
    Example: "2017-02-06T02:37:46Z"

  - `expirationTime` (string)
    [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) / [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp _with_ timezone information
    Example: "2017-02-06T02:37:46Z"

  - `state` (string)
    Enum: "pending", "running", "failed", "completed"

  - `error` (string)

  - `runTime` (string)
    [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) / [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp _with_ timezone information
    Example: "2017-02-06T02:37:46Z"

  - `duration` (number)

  - `createdTime` (string)
    [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) / [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp _with_ timezone information
    Example: "2017-02-06T02:37:46Z"

  - `modifiedTime` (string)
    [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) / [ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) timestamp _with_ timezone information
    Example: "2017-02-06T02:37:46Z"

## Response 400 fields (application/json):

  - `code` (integer, required)
    Example: 404

  - `message` (string, required)
    Example: "Requested resources was not found"

## Response 401 fields (application/json):

  - `code` (integer, required)
    Example: 404

  - `message` (string, required)
    Example: "Requested resources was not found"

## Response 500 fields (application/json):

  - `code` (integer, required)
    Example: 404

  - `message` (string, required)
    Example: "Requested resources was not found"