> 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/fr/portail-dadministration/settings/log-exporter/generic-webhook.md).
# Webhook générique
## Prérequis
Pour ingérer les journaux RADIUSaaS dans un générique **webhook** qui accepte **des corps HTTP structurés en JSON**, un webhook approprié incluant un **URL accessible publiquement** sont requis ainsi que **des identifiants d’authentification,** le cas échéant.
L'exportateur de journaux RADIUSaaS permet l'authentification via une **clé API statique** (encodée dans l’URL, l’en-tête ou le corps).
## Étapes de configuration
Suivez ces étapes pour ajouter un **webhook générique** comme cible d’exportation :
* Accédez à votre **portail d'administration RADIUSaaS**
* Cliquez sur **+ Cible d’exportation**
* Sélectionnez **webhook générique**
* Fournissez un **Nom** et **Description**
* Configurez la **Filtres de messages** selon vos besoins
* Collez l’URL de votre webhook dans le champ **URL du webhook**
* Spécifiez la **méthode HTTP** qui doit être utilisée pour transmettre les données (POST, GET, PUT)
* Ajoutez les **en-têtes HTTP**, par exemple à des fins d’authentification
* Configurez le message **corps** à envoyer à votre 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/fr/portail-dadministration/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.
