Node

Operations for managing output endpoints (IotEndpoints) — reusable, account-level output destinations (Navixy platform or external MQTT broker) that are referenced by Output Endpoint nodes inside flows.

endpointCreate

post

/iot/logic/flow/endpoint/create

Create a new node within a flow. Supports all node types existing in IoT Logic. The node type is specified in the request body's type field.

Authorizations

AuthorizationstringRequired

Enter an API key with the "NVX " prefix, e.g. "NVX 123456abcdefg"

Body

endpointone ofRequired

Endpoint for creation. The type field determines the subtype and the required properties.

or

Responses

200

Successful creation response

application/json

successbooleanRead-onlyOptional

true if request finished successfully

Example: true

idintegerRead-onlyOptional

ID of the created entity

Example: 1723

400

Bad request. The response body carries the API-level error code in status.code. Common codes are 3 for a wrong hash, 4 for an API key that does not exist or a session that has ended, and 7 for invalid parameters, which adds an errors array naming each parameter at fault. It also returns 230 when the endpoint type is not output_mqtt_client, the only type this operation accepts, because the default endpoint is virtual and never stored.

application/json

402

Payment required, code 268: the account has reached its quota for this entity type.

application/json

403

Access denied, code 13: the session lacks the iot_logic_flow right. Code 101 when the call comes from a demo session, which this operation does not accept.

application/json

default

Error response object

application/json

post/iot/logic/flow/endpoint/create

POST /v2/iot/logic/flow/endpoint/create HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 101

{
  "endpoint": {
    "type": "output_default",
    "title": "Navixy Endpoint",
    "status": "active",
    "description": null
  }
}

{
  "success": true,
  "id": 1723
}

endpointRead

post

/iot/logic/flow/endpoint/read

Retrieve detailed configuration for a specific node. Returns complete node data including type-specific configuration, position, and enabled status. Use this endpoint to inspect individual node configuration without retrieving the entire flow.

Authorizations

AuthorizationstringRequired

Enter an API key with the "NVX " prefix, e.g. "NVX 123456abcdefg"

Body

endpoint_idintegerRequired

Endpoint ID in database

Example: 1723

Responses

200

Successful response to read endpoint

application/json

successbooleanRead-onlyOptional

true if request finished successfully

Example: true

valueone ofOptional

Output endpoint — full representation. Use the type field to determine which subtype applies.

or

400

Bad request. The response body carries the API-level error code in status.code. Common codes are 3 for a wrong hash, 4 for an API key that does not exist or a session that has ended, and 7 for invalid parameters, which adds an errors array naming each parameter at fault. It also returns 201 when the endpoint does not exist.

application/json

403

Access denied, code 13: the session lacks the iot_logic_flow right.

application/json

default

Error response object

application/json

post/iot/logic/flow/endpoint/read

POST /v2/iot/logic/flow/endpoint/read HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 20

{
  "endpoint_id": 1723
}

{
  "success": true,
  "value": {
    "id": 12345,
    "type": "output_default",
    "title": "Navixy Endpoint",
    "status": "active",
    "description": null
  }
}

endpointUpdate

post

/iot/logic/flow/endpoint/update

Update an existing node configuration. Requires the complete node object including all required fields for the node type. Changes to nodes in enabled flows take effect immediately and may impact active data processing.

Authorizations

AuthorizationstringRequired

Enter an API key with the "NVX " prefix, e.g. "NVX 123456abcdefg"

Body

endpointone ofRequired

Output endpoint — full representation. Use the type field to determine which subtype applies.

or

Responses

200

Successful response

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

400

Bad request. The response body carries the API-level error code in status.code. Common codes are 3 for a wrong hash, 4 for an API key that does not exist or a session that has ended, and 7 for invalid parameters, which adds an errors array naming each parameter at fault. It also returns 201 when the endpoint does not exist, and 230 when the endpoint type is not output_mqtt_client, the only type this operation accepts, because the default endpoint is virtual and never stored.

application/json

403

Access denied, code 13: the session lacks the iot_logic_flow right. Code 101 when the call comes from a demo session, which this operation does not accept.

application/json

default

Error response object

application/json

post/iot/logic/flow/endpoint/update

POST /v2/iot/logic/flow/endpoint/update HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 101

{
  "endpoint": {
    "type": "output_default",
    "title": "Navixy Endpoint",
    "status": "active",
    "description": null
  }
}

{
  "success": true
}

endpointDelete

post

/iot/logic/flow/endpoint/delete

Permanently delete a node from accoun. Automatically removes all edges connected to this node. Deleting critical nodes (Data Source or Output Endpoint) from enabled flows will interrupt data processing. Verify flow integrity after deletion.

Authorizations

AuthorizationstringRequired

Enter an API key with the "NVX " prefix, e.g. "NVX 123456abcdefg"

Body

endpoint_idintegerRequired

Endpoint ID in database

Example: 1723

Responses

200

Successful response

application/json

successbooleanRead-onlyOptional

true if request finished successfully.

Example: true

400

Bad request. The response body carries the API-level error code in status.code. Common codes are 3 for a wrong hash, 4 for an API key that does not exist or a session that has ended, and 7 for invalid parameters, which adds an errors array naming each parameter at fault. It also returns 201 when the endpoint does not exist.

application/json

403

Access denied, code 13: the session lacks the iot_logic_flow right. Code 101 when the call comes from a demo session, which this operation does not accept.

application/json

default

Error response object

application/json

post/iot/logic/flow/endpoint/delete

POST /v2/iot/logic/flow/endpoint/delete HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 20

{
  "endpoint_id": 1723
}

{
  "success": true
}

endpointList

post

/iot/logic/flow/endpoint/list

List all output endpoints in the user account. Returns a summary view for each endpoint: id, title, type, and description. Use endpointRead to retrieve the full configuration including connection properties for a specific endpoint.

Authorizations

AuthorizationstringRequired

Enter an API key with the "NVX " prefix, e.g. "NVX 123456abcdefg"

Body

objectOptional

Responses

200

Successful response to read a list of endpoints

application/json

successbooleanRead-onlyOptional

true if request finished successfully

Example: true

400

Bad request. The response body carries the API-level error code in status.code. Common codes are 3 for a wrong hash, 4 for an API key that does not exist or a session that has ended, and 7 for invalid parameters, which adds an errors array naming each parameter at fault.

application/json

403

Access denied, code 13: the session lacks the iot_logic_flow right.

application/json

default

Error response object

application/json

post/iot/logic/flow/endpoint/list

POST /v2/iot/logic/flow/endpoint/list HTTP/1.1
Host: api.eu.navixy.com
Authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 2

{}

{
  "success": true,
  "list": [
    {
      "id": 12345,
      "title": "MQTT Endpoint",
      "type": "output_mqtt_client",
      "description": null
    }
  ]
}