Genesis API overview
On this page
The Genesis platform exposes a REST API over HTTPS. Every request is made against one base URL, authenticated with a token in a request header, and answers JSON.
Base URL
https://api.nxgen.cloud/api/v1Every path on these pages is relative to it: GET /user/me means GET https://api.nxgen.cloud/api/v1/user/me.
Authentication
Requests carry a token in the auth-token header. See Authentication for how to obtain one.
Resources
Resource | Operations |
|---|---|
User | 6 |
Account | 11 |
Site | 19 |
Device | 8 |
Sensor | 9 |
Camera Controls | 6 |
Event | 4 |
Event Search | 1 |
IO | 7 |
Trigger | 2 |
Proxy | 1 |
Storage Service | 4 |
Analytics | 4 |
Status View | 2 |
Blog | 6 |
Contact | 4 |
Dashboard | 1 |
Folder | 6 |
Integration | 6 |
Audit | 5 |
Report Template | 3 |
Report | 8 |
Schedule | 2 |
Service Requests | 6 |
Service Request Tab | 2 |
Developer Tools | 1 |
Conventions
- Path parameters are written in braces,
/site/{id}. Replace the whole placeholder, braces included. - Request bodies are JSON unless an operation says otherwise. On these pages a body is shown as a skeleton: the field names with the type expected in place of each value, and
(required)on the fields that must be present. - Response tables list every status the specification declares.
401means the token was missing or rejected;403means it was valid but not entitled to the resource.
Specification version 1.0.0.
Thank you — your feedback goes to the team that owns this page.