---
title: "Dua Readiness"
method: GET
path: "/api/declarations/dua-readiness"
tags: ["Declarations"]
---

# Dua Readiness

`GET /api/declarations/dua-readiness`

Per-entity readiness check for DUA generation.

For each ID provided, returns the hydrated entity data (already shaped
for the DUA template) plus a list of required fields that are empty.
Frontend uses this to drive completeness chips and the "what's missing"
expandable panel on /dua-declarations.

Multi-tenancy: company_id is taken from the JWT and passed to every DB
function. PV identity hydration is gated behind the banking lookup
(which enforces IDempresa) so a foreign PV can never leak.

## Query parameters

- `sujeito_ativo_id` integer, nullable
- `sujeito_passivo_id` integer, nullable
- `vehicle_id` integer, nullable
- `restituicao_pv_id` integer, nullable

## Headers

- `x-api-token` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/4b44eb76b3ee/schema)