---
title: "Verify a preserved package"
method: GET
path: "/api/v1/rest/conservazione/packages/{id}/verification"
tags: ["Legal preservation"]
---

# Verify a preserved package

`GET /api/v1/rest/conservazione/packages/{id}/verification`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/rest/conservazione/packages/{id}/verification`
- Auth: HTTP bearer

Re-read the container from the WORM store and check its digest, the index digest, the seal and the inclusion path against the recorded root. Records the outcome (positive ones too).

**Examples**

- Verifica che il pacchetto 0b1c… sia ancora integro
  `GET /api/v1/rest/conservazione/packages/0b1c2d3e-0000-4000-8000-000000000000/verification`

## Path parameters

- `id` string, uuid, required

## Headers

- `X-Tenant-Id` string, uuid

## Response `200`

Done. `data` is the tool’s own answer.

- RestResult
  - `ok` true, required
  - `data` unknown, required

## Other responses

- `400`: The arguments did not validate: `error.message` names the field, what it expects and what arrived.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The call never ran: the module is off for this organisation, the credential lacks the permission or the module, the tier does not cover it, or the tool is destructive and the key was not minted for that.
- `404`: Nothing with that id in this organisation.
- `422`: The tool ran and refused, in a sentence of its own (`TOOL_REFUSED`): the message says what to change. Retrying the same call will not help.
- `429`: The API key has spent its minute, or its day. Every request a key makes counts. See `Retry-After`.

---

[API](https://skmtc.dev/custodo/apis/custodo-integrazioni.md) · [All operations](https://skmtc.dev/custodo/apis/custodo-integrazioni/llms.txt) · [OpenAPI document](https://skmtc.dev/custodo/apis/custodo-integrazioni/revisions/16d336d3ec2a?raw)