> 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/qna/using-navixy/send-data-from-a-non-integrated-device-navixy-generic-protocol.md).

# Send data from a non-integrated device (Navixy Generic Protocol)

Convert device data to Navixy JSON format and send it over HTTP/HTTPS using the Navixy Generic Protocol for non-integrated hardware

## Question

How can I send data to the platform from a non-integrated device?

## Answer

If your specific device isn't integrated with the Navixy platform, you can use our Navixy Generic Protocol to do so. This is a universal protocol allowing you to send the specific data you need to our platform without waiting or paying for the costs associated with device integration. Once you have your device data, you will need to "convert" it to Navixy's accepted JSON format as shown in the documentation. Then all you have to do is send the data over HTTP/HTTPS to our platform and your device data will display.

The minimum required JSON is as follows:

| { "message\_time": "...", "device\_id": "..." } |
| ----------------------------------------------- |

## Links

* [Navixy Generic Protocol](/docs/iot-logic-api/technologies/navixy-generic-protocol.md)
* [Message structure and attributes](/docs/iot-logic-api/technologies/navixy-generic-protocol/message-structure-and-attributes.md)


---

# 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/qna/using-navixy/send-data-from-a-non-integrated-device-navixy-generic-protocol.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.