/getting-started/index.html Getting access In order to get programmatic access to the data from the devices an API key is needed. Alternatively user credentials to our admin interface can be used. API keys and user credentials can be obtained from Neura by getting in touch with one of our sales rep or emailing n2n-dl-support@nnnco.com.au. In the following examples we assume that the following test API key: 8a0892e3aedbe2f2ade4bd727d4725e0c639d021 - which is no longer valid - is linked to an enterprise called n-hub.client1. Hugo en Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/api-structure/index.html Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/api-structure/index.html API Structure The N-Hub APIs are organized around REST and have a predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors. JSON is returned by all API responses, including errors. The APIs are designed to be easy to integrate with so we currently do not provide API client libraries. This may change in the future. Authentication Currently 2 different authentication models are supported: client credentials and API key /getting-started/data-model/index.html Mon, 01 Jan 0001 00:00:00 +0000 /getting-started/data-model/index.html The N-Hub data model is built around devices, users or API keys and groups Devices In N-Hub Sensors and actuators are all considerd devices. All devices support data uplink - sending data to N-Hub - but only some devices have downlink capabilities for remote control or configuration. Most devices on the market come with multiple sensors. To support this N-Hub groups device readings - where the parsing takes place - in channels (one per sensor).