List Verdict Overrides
Every finding on the record's current version. Read-only, and
the only endpoint here that needs just eudr:read.
Ordered by axis, then subject_type, then subject_id, then
created_at โ a total order, so the same record always lists in the
same sequence. subject_id sorts ahead of created_at on purpose:
two findings written in one statement share created_at at
millisecond resolution, which would otherwise leave their order up
to the query plan.
โถQuery params
| Param | Description |
|---|---|
axis | Optional. Return only plot_compliance, legality, or exclusion. Any other value answers 400. |
There is no pagination โ a record holds one finding per
(axis, subject), so the list is bounded by the version's plot
count.
โถExpired findings are included
This endpoint returns findings whatever their validity window, including ones that have already expired. That is deliberate: the window retires a finding, it does not erase it, and the audit trail has to keep showing what was attested and when.
So a row in this list is not proof that a finding is in force.
Compare valid_from / valid_to against now:
active โบ (valid_from is null or โค now)
and (valid_to is null or โฅ now)
To see the effective verdicts instead โ the ones the submit gate
and TRACES will use โ read the plot register on
GET /:recordId/report, which applies the window for you.
โถVersion scope
The list is scoped to the current version. Cutting a new version carries findings forward, with plot ids remapped if a re-ingest changed them, so the same findings appear against the new version's subject ids. To read a filed version's findings as filed, use the version-pinned report.
โถErrors
| Status | Code | When |
|---|---|---|
| 400 | BAD_REQUEST | axis is not one of the three values |
| 401 | UNAUTHORIZED | Missing or invalid API key |
| 403 | FORBIDDEN | Key lacks eudr:read |
| 404 | NOT_FOUND | Record is not visible to the caller |
Required scope:
eudr:read