Most controllers in this category make you choose: their platform, or raw data shipped somewhere you have to build. Genesis comes with OmniCloud, and with a REST API that covers what the dashboard covers, so your own system can be the front end from the first day.
List devices, read their state, and set what each port reads and how often, the same settings the dashboard changes.
Pull readings by device, sensor and time range into your own database, reports or customer portal.
Fire outputs, manage users and accounts, and share devices between accounts, with tokens scoped to exactly what an integration needs.
| Style | REST over HTTPS |
|---|---|
| Authentication | Bearer tokens, scoped to a subset of the owner's permissions |
| Token lifecycle | Expiry and revocation |
| Exports | Excel files, from the dashboard and the API |
Give the integration only the permissions it needs, for example read access to one account's readings.
Start by polling readings on a schedule that matches the device reporting interval. Ask us about the integration you have in mind before building around push delivery.
The API serves what the devices have sent. A battery unit transmitting once a day has its readings in the cloud once a day.
Tell us what you are connecting and we walk you through the endpoints it needs, before you write the first line against them.
No. The API covers what the dashboard covers, so your own system can be the only front end your users see.
Yes. A token carries a subset of its owner's permissions, so it can be scoped to one account and read only.
Yes. The control commands that fire an output are part of it.
The sensors, how many points, where they sit, and whether there is power and coverage. We come back with whether the ports cover it and what the installation looks like.
Talk to us →