---
title: "List Tasks"
method: GET
path: "/api/companies/{company_uuid}/tasks"
tags: ["tasks"]
---

# List Tasks

`GET /api/companies/{company_uuid}/tasks`

## Request

- Base URL: `https://api.regdoor.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.regdoor.com/api/companies/{company_uuid}/tasks`
- Auth: HTTP bearer

Lists the Tasks the caller can see — membership in a Task's área or
owner Group, same visibility rule as GET one Task.

## Path parameters

- `company_uuid` string, uuid, required

## Query parameters

- `status` TaskStatusEnum[]: Filter by status. Can specify multiple times.
- `group_uuid` string[]: Filter by área Group UUID. Can specify multiple times.
- `atraso` 'no_prazo' | 'atencao' | 'atrasado', nullable: Filter by the worst of each Task's 4 compute_atraso axes — the Tasks list's stage-counter sub-filter.
- `search` string, nullable: Case-insensitive match on the linked content name.
- `collection_list` string[]: Filter by collection name(s). Can specify multiple times.
- `size` integer: Page size
- `page` integer: Page number

## Headers

- `X-Teamspace-Uuid` string, uuid, nullable
- `X-User-Email` string, nullable
- `X-User-Name` string, nullable

## Response `200`

Successful Response

- PageTaskListItemResponse
  - `items` TaskListItemResponse[], required
    - `uuid` string, uuid4, required
    - `content_uuid` string, uuid4, required
    - `content_name` string, required
    - `group_uuid` string, uuid4, required
    - `group_name` string, required
    - `owner_group_uuid` string, uuid4, required
    - `owner_group_name` string, required
    - `status` 'sugerido' | 'aprovado_para_envio' | 'enviado_a_area' | 'em_analise_pela_area' | 'aguardando_aprovacao_juridico' | 'devolvido' | 'conforme' | 'nao_conforme' | 'nao_aplicavel' | 'ciencia_registrada' | 'em_execucao' | 'aguardando_aprovacao_conclusao', required: Compliance Workflow v1 Task macro-status. `sugerido` still belongs to the (future, out of scope) relevance/routing engine. `aprovado_para_envio` is the real "waiting on Jurídico" pre-send state for a `informativo=False` Task created by the Regulatory evaluation drawer: Jurídico fills `prazo_atual` (and optionally `assunto_principal`/`criticidade`/`analise_juridico_regulatorio`) then sends it on to the área (see `task_state_machine.send_task_to_area`).
    - `criticidade` 'alta' | 'media' | 'baixa'
    - `assunto_principal` string, nullable
    - `prazo_atual` string, date, nullable
    - `created_at` string, date-time, required
    - `atraso` TaskAtrasoFlags, required: Derived, read-time-only SLA indicators (`task_state_machine. compute_atraso`) — never persisted on TaskModel. Each axis is `"no_prazo" | "atencao" | "atrasado"`, independent of `task.status`.
      - `juridico_triagem` 'no_prazo' | 'atencao' | 'atrasado', required
      - `juridico_aprovacao` 'no_prazo' | 'atencao' | 'atrasado', required
      - `area` 'no_prazo' | 'atencao' | 'atrasado', required
      - `vigencia_norma` 'no_prazo' | 'atencao' | 'atrasado', required
  - `total` integer, nullable, required
  - `page` integer, nullable, required
  - `size` integer, nullable, required
  - `pages` integer, nullable

## Other responses

- `404`: Not found
- `422`: Validation Error

---

[API](https://skmtc.dev/regdoor/apis/regdoor-api.md) - [All operations](https://skmtc.dev/regdoor/apis/regdoor-api/llms.txt) - [OpenAPI document](https://skmtc.dev/regdoor/apis/regdoor-api/revisions/7642336631af?raw)