> For the complete documentation index, see [llms.txt](https://docs.floui.io/guia/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.floui.io/guia/conectores/categorias/servicos-externos/wake-commerce/usuario/remover-o-vinculo-entre-o-usuario-e-o-parceiro.md).

# Remover o vinculo entre o usuário e o parceiro

Remove um vinculo entre parceiro e usuário na Wake Commerce.

{% tabs %}
{% tab title="Parâmetros" %}

<table><thead><tr><th width="224">Campo</th><th width="137">Tipo</th><th>Descrição</th></tr></thead><tbody><tr><td>Descrição</td><td>Campo de texto</td><td>Mensagem visual usada para descrever a funcionalidade do conector dentro do fluxo.</td></tr><tr><td>Token</td><td>Campo de texto</td><td>O token é gerado através da plataforma administrativa do lojista.</td></tr><tr><td>E-mail do usuário</td><td>Campo de texto</td><td>E-mail do usuário, cadastrado na Wake, que será desvinculado do parceiro.</td></tr><tr><td>Número identificador do parceiro</td><td>Campo de texto</td><td>Identificador do parceiro, cadastrado na Wake, que terá o vinculo com usuário removido.</td></tr><tr><td>Output path</td><td>Campo de texto</td><td>Armazena os dados de saída do conector ao final da execução.</td></tr></tbody></table>
{% endtab %}

{% tab title="Detalhes" %}

## Detalhes

O conector possibilita a remoção do vínculo estabelecido entre parceiros e usuários na Wake, por meio da API REST.&#x20;

O conector utiliza o endpoint **DELETE** `https://api.fbits.net/usuarios/{email}/parceiro`, removendo o vinculo entre usuário e parceiro através do e-mail do usuário e o identificador único do parceiro.

Para mais informações sobre essa e outras APIs disponíveis na Wake Commerce, consulte as [Referências da API](https://wakecommerce.readme.io/reference/remove-o-vinculo-entre-usuario-e-parceiro).
{% endtab %}
{% endtabs %}


---

# 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.floui.io/guia/conectores/categorias/servicos-externos/wake-commerce/usuario/remover-o-vinculo-entre-o-usuario-e-o-parceiro.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.