> 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/iot-logic-api/technologies.md).

# TECHNOLOGIES

- [Navixy Generic Protocol](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol.md): Send device telemetry to Navixy using NGP, an open JSON telematics protocol. Start with the quick-start, then see transport, encoding, and message format.
- [Transport layer](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol/transport-layer.md): Connect to Navixy via HTTP/HTTPS or MQTT to send NGP messages. Regional endpoint URLs, connection parameters, and code examples for both transport methods.
- [Data types and encoding standards](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol/data-types-and-encoding-standards.md): Map JSON types to NGP fields, format timestamps as ISO 8601 UTC, and encode binary values as Base64. Covers size limits and constraints for each data type.
- [Message structure and attributes](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol/message-structure-and-attributes.md): Define NGP message payloads using mandatory and optional attributes: location, events, mobile cells, Wi-Fi, device motion, sensors, I/O, and custom fields.
- [Predefined event identifiers](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol/predefined-event-identifiers.md): Standard event\_id values for NGP messages, covering power, security, safety, vehicle efficiency, track, I/O, and peripheral events.
- [NGP Mapper skill](https://navixy.com/docs/iot-logic-api/technologies/navixy-generic-protocol/ngp-mapper-skill.md): Use the NGP Mapper Claude skill to generate a ready-to-implement field mapping from any device or telematics platform format to Navixy Generic Protocol.
- [Navixy IoT Logic Expression Language](https://navixy.com/docs/iot-logic-api/technologies/navixy-iot-logic-expression-language.md): Write JEXL-based expressions in IoT Logic flows to transform raw device data, compute custom attributes, and route telemetry conditionally in logic nodes.
- [Expression syntax reference](https://navixy.com/docs/iot-logic-api/technologies/navixy-iot-logic-expression-language/expression-syntax-reference.md): Full syntax reference for the IoT Logic Expression Language: literals, operators, attribute access, built-in functions, data types, and null handling rules.
- [Formula error reference](https://navixy.com/docs/iot-logic-api/technologies/navixy-iot-logic-expression-language/formula-errors.md): Human-readable explanations for all JEXL formula validation error messages in Navixy IoT Logic, with causes and corrected examples.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://navixy.com/docs/iot-logic-api/technologies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.