> For the complete documentation index, see [llms.txt](https://docs.radiusaas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiusaas.com/pt/portal-de-administracao/settings/log-exporter/generic-webhook.md).
# Webhook genérico
## Pré-requisitos
Para ingerir logs do RADIUSaaS num webhook genérico **webhook** que aceite **corpos HTTP estruturados em JSON**, é necessário um webhook adequado, incluindo um **URL publicamente disponível** bem como **credenciais de autenticação,** se aplicável.
O RADIUSaaS Log Exporter permite autenticação através de uma **chave de API estática** (codificada na URL, no cabeçalho ou no corpo).
## Passos de configuração
Siga estes passos para adicionar um **Generic Webhook** destino de exportação:
* Navegue até ao seu **Portal de Administração do RADIUSaaS**
* Clique em **+ Destino de Exportação**
* Selecione **Generic Webhook**
* Forneça um **Nome** e **Descrição**
* Configure o **Message Filters** adaptado às suas necessidades
* Cole o URL do seu webhook no campo **Webhook URL**
* Especifique o **método HTTP** que deverá ser usado para transmitir os dados (POST, GET, PUT)
* Adicione os **cabeçalhos HTTP**relevantes, por exemplo, para fins de autenticação
* Configure o **Body** da mensagem a ser enviado para o seu webhook
---
# 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.radiusaas.com/pt/portal-de-administracao/settings/log-exporter/generic-webhook.md?ask=&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.
