---
title: "Download the completion certificate as PDF"
method: GET
path: "/api/v1/firme/{id}/certificate"
tags: ["Signatures (app routes)"]
---

# Download the completion certificate as PDF

`GET /api/v1/firme/{id}/certificate`

## Request

- Base URL: `https://api.custodo.ai`
- URL: `https://api.custodo.ai/api/v1/firme/{id}/certificate`
- Auth: HTTP bearer

Who was asked, how each signer was reached and authenticated, from where and when, the seal of each signature, both SHA-256 digests, the verdict and the whole evidence chain — with the Custodo signature ID also stored in the PAdES signature reason. After completion a background job freezes the evidence through completion, saves the PDF in the tenant locale and files the identical bytes in Archive, regardless of archiveOnComplete. Poll hasCertificate; certificateDocumentId names its Archive document. Interim and historical attestations without a saved certificate render in lang. Every download is audited.

## Path parameters

- `id` string, uuid, required

## Query parameters

- `lang` 'it' | 'en'

## Headers

- `X-Tenant-Id` string, uuid

## Response `200`

The attestation.

## Other responses

- `400`: The request did not validate: `error.details` names the fields.
- `401`: No API key, or one that is malformed, unknown, revoked or expired.
- `403`: The module is off for this organisation, the credential lacks the permission, or the tier does not cover it.
- `404`: Nothing with that id in this organisation.
- `429`: The API key has spent its minute, or its day. 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)