The NEX cloud API is an interface between any controller/product/front-end and our cloud system. The first version of our API is at https://nexcloud.io/v1.0. It is through this API that you will be able to get information about your product's configuration and setup, retrieve your data, and provide an online access point for customers looking to view data from your product anytime, anywhere.
Some general terminology used in the NEX system:
| Account | Your company or organisation in the NEX system. Your users, hardware, data, and billing are attributed to your Account. |
|---|
| User | An individual user login with their own dashboard and access to you Account. |
|---|
| Site | A building or location where hardware is installed. This makes it convenient to organise your Controllers and their data. |
|---|
| Controller | Any system that connects to the API for the purpose of acquiring and sending data (i.e. NEX hardware installed on your site). |
|---|
| Device | An object that communicates or is within the Controller from which you gather data (i.e. a power meter on your site). |
|---|
| Data Point | A data point is any single data providing element on your device/devices. |
|---|
For example:
- A product that reads data via Modbus and sends it to the NEX Cloud would be the Controller. The systems it talks to on the Modbus LAN would be the Devices. One of these devices may be reading the temperature, pressure, and humidity of the room it is in. Each of these measurements would be a Data Point.
- A product that connects to the NEX Cloud, as well as reading data from its own inputs could be split up into a Controller and Device. The Controller would be its HTTPS functionality, whilst the Device would be its ability to read data from its inputs, which would be the Data Points