> For the complete documentation index, see [llms.txt](https://docs.zapsign.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zapsign.com.br/zapsign-api/espanol/firmantes/excluir-signatario.md).

# Eliminar firmante

Delete a signer from the document.

{% hint style="danger" %}
**The deletion is irreversible**. If you want to reinsert the signer into the document, he will have a new token/URL to sign.
{% endhint %}

{% hint style="info" %}
El método de la solicitud es `DELETE`. Si usas un `GET` o `POST` no va a tener efecto. 
{% endhint %}

## Eliminar firmante

<mark style="color:red;">`DELETE`</mark> `https://api.zapsign.com.br/api/v1/signer/{{signer_token}}/remove/`

**Requisitos previos:**&#x20;

* No es posible eliminar un firmante que ya haya firmado el documento.&#x20;
* No es posible eliminar al único firmante del documento. Si necesitas hacerlo, primero agrega un segundo firmante y luego elimina al primero.&#x20;

**Sobre los webhooks:** En algunas situaciones, el webhook "doc\_signed" podría activarse después de que se haya eliminado un firmante. Si esto ocurre, el archivo PDF signed\_file ya habrá sido actualizado.

#### Encabezado

<table><thead><tr><th width="175">Nombre</th><th width="103">Tipo</th><th>Descripción</th></tr></thead><tbody><tr><td>Authorization<mark style="color:red;">*</mark></td><td>string</td><td>API token prefijo con la palabra "Bearer". Ex: Bearer c7f35c84-7893-4087-b4fb-d1f06c23</td></tr></tbody></table>

{% tabs %}
{% tab title="200 Signer removed successfully." %}

{% endtab %}
{% endtabs %}

### Ejemplo de una solicitud en Postman

{% embed url="<https://www.postman.com/zapsign/workspace/zapsign-workspace/request/27495556-f2604fc9-736f-4aaa-aece-8e53674637f2?ctx=documentation>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zapsign.com.br/zapsign-api/espanol/firmantes/excluir-signatario.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.