Reprocessing Documents and Webhooks

In scenarios where integration failures, validation errors, or the need for updates to the receiving system occur, reprocessing webhooks can be crucial to ensure correct data delivery and maintain consistency between integrated systems.

In this section:

• Reprocessing webhooks via the web interface

• Reprocessing webhooks and documents via API

---

Reprocessing webhooks via Web

To reprocess signed documents via the web interface, navigate to the documents tab, find your document, click the gear icon, and select "Reprocess Webhooks."

Interface with options for managing a signed document, including adding signers, editing fields, and reprocessing the webhook.

---

Reprocessing Documents and Webhooks via API

In cases where the signed document needs to be regenerated—such as when there are integrity issues with the file or a failure in webhook delivery—you can use the reprocessing endpoint. This is useful, for instance, when the final document was corrupted or the associated webhook was not properly sent.

POSThttps://api.zapsign.com.br/api/v1/docs/{{doc_principal_token}}/reprocess-doc/

Headers

Name	Type	Description
Authorization*	string	Api token a frente do texto "Bearer".Ex: Bearer c7f35c84-7893-4087-b4fb-d1f06c23

Request Body

{
    "send_webhook": true,
    "resign_doc": false
}

Name	Type	Description
send_webhook	boolean	To activate the resending of the webhook of the selected document. Default: false
resign_doc	boolean	To reprocess the signed document by creating a new pdf of the selected document. Default: false

Response

200-OK

Document successfully reprocessed.

404- Not found

Check if the document token is correct in the URL.

Since the process is asynchronous, monitor the webhooks or manually check the document status after a few minutes.