API reference

Browse IoT Logic API endpoints for flow and endpoint management. Covers authentication, regional base URLs, and the full OpenAPI specification.

The IoT Logic API allows you to programmatically manage data flows and endpoints for processing IoT device data. Create flows, configure nodes, and route data between different systems.

BETA Version This API is in early access. Functionality may change in future updates.

Overview

The API is organized around two main resource types:

Flows - Manage data processing workflows. Learn more about flow concepts and structure in our technical overview.

Endpoints (Nodes) - Configure input and output endpoints for data routing. Understand different node types and their configuration in the core concepts documentation.

Looking for node schemas and examples? See Nodes (includes the Webhook node for HTTP integrations).

For a complete walkthrough, see Quick start: create your first flow.

Authentication

All requests require authentication using an API key with the NVX prefix in the Authorization header (space-separated: Authorization: NVX <key>). See the authentication guide for which credential to use and how to obtain one.

Base URLs

• European platform: https://api.eu.navixy.com/v2

• American platform: https://api.us.navixy.com/v2

• Middle East platform: https://api.me.navixy.com/v2

OpenAPI spec

Under this section you can find a complete and interactive API reference generated from an up-to-date OpenAPI specification. There you can discover endpoint paths, parameters, object schemas (models), and test API calls right from the documentation. You can also download the raw OpenAPI specification as JSON.

Quick endpoint reference

The Navixy IoT Logic API provides the following endpoints for managing flows and endpoints:

Flow management endpoints

Endpoint	Method	Description	Key Parameters
/iot/logic/flow/create	POST	Create a new flow	flow object with title, nodes, edges
/iot/logic/flow/read	GET	Read an existing flow	flow_id
/iot/logic/flow/update	POST	Update an existing flow	flow object with id, title, nodes, edges
/iot/logic/flow/delete	POST	Delete a flow	flow_id
/iot/logic/flow/list	GET	List all flows	none
/iot/logic/flow/export	GET	Export an existing flow	flow_id
/iot/logic/flow/sources/mapping/list	GET	List all device-to-flow assignments	none
/iot/logic/flow/sources/list	GET	List the device IDs feeding a specific flow	flow_id
/iot/logic/flow/sources/attribute/list	POST	List telemetry attributes available for authoring expressions	source_ids (optional)
/iot/logic/flow/template/list	GET	List all system-provided flow templates	none
/iot/logic/flow/template/read	GET	Retrieve a single system-provided flow template	flow_id (template ID)
/iot/logic/flow/push	POST	Send external data into a connector-configured Data Source node	flow_id, node_id, plus the fields to merge
/iot/logic/flow/schema/read	GET	Retrieve the JSON Schema definition for all node types	none

The schema returned by /iot/logic/flow/schema/read describes the Navixy UI form's validation rules, not a guaranteed write-API contract. flowCreate and flowUpdate don't enforce every constraint it lists. For example, a field marked required in the schema may be silently defaulted instead of rejected.

Node management endpoints

Endpoint	Method	Description	Key Parameters
/iot/logic/flow/endpoint/create	POST	Create a new endpoint	endpoint object with type, title, properties
/iot/logic/flow/endpoint/read	POST	Read an existing endpoint	endpoint_id
/iot/logic/flow/endpoint/update	POST	Update an existing endpoint	endpoint object with id and updated fields
/iot/logic/flow/endpoint/delete	POST	Delete an endpoint	endpoint_id
/iot/logic/flow/endpoint/list	POST	List all endpoints	none

Support

For questions and support, contact [e-mail].