---
title: "Restamps"
description: "Digiploma restamps: how signed XML files get a new archive timestamp before the timestamp authority certificate expires, keeping signatures verifiable."
canonical: "https://docs.lacunasoftware.com/en-us/articles/digiploma/api/restamps"
locale: "en"
product: "Digiploma"
last_updated: "2026-10-11"
---

# Restamps

The signatures of a diploma must remain verifiable long after the certificates that created them expire. Each signed XML file therefore
carries an archive timestamp (ICP-Brasil AD-RA policy), whose own validity ends when the certificate of the timestamp authority expires.
Before that happens, Digiploma **restamps** the file (*renotarização*): it adds a new archive timestamp, which extends the preservation of
the signatures.

This happens automatically, for the signed XML files of:

* diplomas (the diploma XML and the academic documentation XML);
* final academic transcripts and second copies (not partial transcripts);
* curriculums;
* registration requests (the diploma XML signed by the registrar), only when the instance enables it.

When a document is concluded, Digiploma creates a **restamp record** with the expiration date of its archive timestamp. A daily job, at
night (Brasília time, by default), restamps the files whose expiration is less than 180 days away (by default), then creates a new record for
the new expiration date. On premises, these defaults are [configurable](https://docs.lacunasoftware.com/en-us/articles/digiploma/on-premises/settings#restamp-and-timestamp-settings).
A restamp that fails is retried on the following days. Restamping is on by default; the instance administrator can turn it off for an
organization. [Diploma revalidation](https://docs.lacunasoftware.com/en-us/articles/digiploma/revalidation) explains why it is needed, with a diagram of the cycle.

## List restamps

`GET /api/restamps` returns a page of the organization's restamp records. It requires the `ViewRestamp` permission.

| Parameter | Description |
|---|---|
| `DocumentTypes` | Document types, repeatable: `Degree`, `AcademicDocumentation`, `Registration`, `AcademicTranscript`, `Curriculum`. |
| `Status` | `Restamped` (applied), `NonRestamped` (pending) or `WithError`. |
| `RestampFilterField` | The date that `StartDateUtc`, `EndDateUtc` and the order refer to: `ExpiringDate` (default), the expiration of the archive timestamp, or `RestampDate`, when it was restamped. |
| `StartDateUtc`, `EndDateUtc` | From `StartDateUtc` (inclusive) until `EndDateUtc` (exclusive). |
| `Q` | Text in the identifier. |

Besides the [paging parameters](https://docs.lacunasoftware.com/en-us/articles/digiploma/api#pagination).

| Field | Description |
|---|---|
| `id` | The record. |
| `documentType`, `documentId` | The document. For `Degree` and `AcademicDocumentation`, `documentId` is the diploma's id. |
| `identifier` | The student's CPF, or the code of a curriculum. |
| `archivingExpiringDate` | When the current archive timestamp expires. |
| `date` | When the file was restamped; `null` while pending. |
| `errorReason` | The error, if the record could not be created or the restamp failed. |
| `creationDate`, `updateDate` | |

## Webhooks

`RestampCreated`, `RestampUpdated`, `RestampApplied` and `RestampApplyingError` report the progress of each record, but they are disabled
by default and are sent only when the instance enables them. See [Webhooks](https://docs.lacunasoftware.com/en-us/articles/digiploma/api/webhooks).