> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/expert-center/fr/faq-and-troubleshooting/gps-devices/integrate-iot-data-from-servers-and-gateways.md).

# Intégrer les données IoT des serveurs et des passerelles

Recevez des données de télématique provenant de passerelles et de serveurs tiers à l'aide des protocoles Wialon Retranslator, Combine et IPS de retransmission dans Navixy.

Navixy peut recevoir des données télématiques non seulement directement depuis les appareils, mais aussi via des protocoles de retransmission pris en charge provenant d’autres plateformes et passerelles. Cela permet une approche flexible et complète de l’intégration des données, garantissant la compatibilité avec divers services.

Navixy prend en charge plusieurs protocoles :

* [Protocoles Wialon pour l’ingestion des données](/docs/expert-center/fr/faq-and-troubleshooting/gps-devices/integrate-iot-data-from-servers-and-gateways/wialon-protocols-for-data-ingestion.md)**:** Wialon Retranslator, Wialon Combine et Wialon IPS.

Chaque protocole possède des capacités uniques, permettant aux utilisateurs de transmettre un large éventail de données et de télémétrie vers la plateforme Navixy.


---

# 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://navixy.com/docs/expert-center/fr/faq-and-troubleshooting/gps-devices/integrate-iot-data-from-servers-and-gateways.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.