> ## Documentation Index
> Fetch the complete documentation index at: https://developers.projectcor.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Tasks

> Retrieves a paginated list of tasks. By default, responses are paginated with 20 items per page.



## OpenAPI

````yaml /api-reference/openapi.json get /tasks
openapi: 3.1.0
info:
  title: COR API
  description: >-
    The COR API lets you integrate with projectcor.com applications using simple
    HTTP methods, in either XML or JSON formats, making this an ideal API for
    developing integrations with other softwares, external clients or mobile
    applications
  version: 1.0.0
servers:
  - url: https://api.projectcor.com/v1
    description: Production server
security:
  - bearerAuth: []
paths:
  /tasks:
    get:
      tags:
        - Tasks
      summary: Get Tasks
      description: >-
        Retrieves a paginated list of tasks. By default, responses are paginated
        with 20 items per page.
      parameters:
        - name: page
          in: query
          schema:
            type:
              - integer
              - boolean
            default: 1
          description: 'Page number (default: 1). Set to `false` to disable pagination.'
        - name: perPage
          in: query
          schema:
            type: integer
            default: 20
          description: 'Number of items per page (default: 20).'
        - name: filters
          in: query
          schema:
            type: string
          description: >-
            Filters for the task list, expressed as a JSON object
            **URL-encoded** into this query string.


            **Examples of common keys**


            - **`projects`** — One project ID, or an array of project IDs.

            - **`pm`** — One user ID, or an array of user IDs for the task PM.

            - **`status`** — One status or several; examples: `nueva`,
            `en_proceso`, `finalizada`.


            **Other supported keys** in the same object include `labels`,
            `categories`, `clients`, `collaborator`, `priority`, and `sprints`.


            **Important:** Use only this parameter for filtering. Do **not** add
            extra query parameters such as `?project_id=` or `?user_id=`.
        - name: order
          in: query
          schema:
            type: string
          description: >-
            Optional sort specification as a JSON object **URL-encoded** into
            this query string.


            For each field you want to sort by, set the value to **`ASC`** or
            **`DESC`** (where supported).


            **Sortable fields** include `client`, `project`, `task`, `deadline`,
            `datetime`, `pm`, `priority`, and `sprint`.


            The response also uses a default tie-breaker: the task's defined
            order ascending.
      responses:
        '200':
          description: Paginated list of tasks
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaginatedTasksResponse'
components:
  schemas:
    PaginatedTasksResponse:
      type: object
      description: Paginated response for tasks list
      properties:
        total:
          type:
            - string
            - integer
          description: Total number of tasks
        perPage:
          type: integer
          description: Number of items per page
        page:
          type: integer
          description: Current page number
        lastPage:
          type: integer
          description: Last available page number
        data:
          type: array
          description: Array of tasks for the current page
          items:
            $ref: '#/components/schemas/Task'
    Task:
      type: object
      properties:
        id:
          type: integer
        title:
          type: string
        project_id:
          type: integer
        description:
          type: string
        deadline:
          type: string
          format: date-time
        status:
          type: string
          enum:
            - nueva
            - en_proceso
            - estancada
            - finalizada
        priority:
          type: integer
          enum:
            - 0
            - 1
            - 2
            - 3
          description: 0 = Low, 1 = Medium, 2 = High, 3 = Urgent
        archived:
          type: boolean
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````