Navixy IoT Logic API

Introduction

Navixy IoT Logic is a no-code/low-code tool that enables seamless IoT data processing and integration. Its API provides programmatic access to create, manage, and optimize data flows between IoT devices and destination systems without requiring extensive development resources.

Purpose and core capabilities

Navixy IoT Logic functions as a data flow manager that:

• Receives information from devices connected to the platform

• Decodes and converts data in real-time

• Sends processed data to other platforms and services

• Enables building complex flows with nodes responsible for specific data processing tasks

The IoT Logic API allows developers and system integrators to programmatically implement these capabilities, making it effective for organizations that need to:

• Work efficiently with decoded device data

• Apply flexible data transformation to match specific business needs

• Monitor and troubleshoot data streams

• Create consistent data flows across multiple devices and protocols

Key concepts

Navixy IoT Logic operates based on two fundamental components that work together to process device data:

Flow

A Flow is the foundation for all data logic in the product. It defines how data moves through stages of reception, enrichment, and transmission. Each flow consists of connected nodes that determine what happens to the data at each processing stage.

Key characteristics of flows:

• Flows can be enabled or disabled to control data processing

• Every flow requires at least one data source and one output endpoint

• Each device can only be assigned to one flow at a time

• Flows process data in real-time as it arrives from devices

Nodes

Nodes are the functional elements of a flow, with each node handling a specific stage of the data lifecycle. There are three primary types of nodes:

• Data Source node: Receives data from M2M devices and serves as the entry point for all device data

• Initiate Attribute node: Processes and enriches incoming data, including creating new calculated attributes trough mathematical operations in

• Output Endpoint node: Transmits data to target systems using the . This node can be configured to use different endpoint types:

Nodes are connected through transitions (edges) that define the path data follows through the flow.

Data flow architecture

The following screenshot from IoT Logic UI illustrates the basic architecture of a flow in IoT Logic:

This represents a simple linear flow where:

1. The Data Source node collects telemetry from selected devices

2. The Initiate Attribute node processes and enriches this data

3. The Default Output Endpoint node delivers the transformed data to its destination - Navixy platform

More complex architectures can be created by:

• Adding multiple data source nodes to process different device types

• Chaining multiple attribute nodes for multi-stage data processing

• Including several output endpoints to deliver data to multiple destinations outside Navixy simultaneously

Quick start for IoT Logic API

To ensure a clear picture of the basic IoT Logic API capabilities, let's create your first flow.

The following example demonstrates how to create a complete flow with three nodes that sends data to Navixy. This flow will:

1. Collect data from specified devices

2. Calculate temperature in Fahrenheit from Celsius readings

3. Send the enriched data to the Navixy platform

Step 1: Authentication

First, authenticate to obtain a session token. To do it, send a POST request to the user authentication endpoint {baseURL}/v2/user/auth providing your account's login and password as parameters:

Response (example):

Copy the hash value from the response.

Step 2: Create a complete flow with nodes and connections

Create a flow with all nodes and connections in a single request:

Response (example):

Parameters explained

• Flow entity: The main container defining a complete data processing pipeline

  • title: Names your flow for easier identification

  • enabled: When true, flow begins processing data immediately after creation