Welcome to the FAQ section for RESET Data Providers.
Click here to go back to RESET Data Providers.
Click here to go back to the FAQ list.
1. Accreditation Process
Yes. Please refer to the instructions in the RESET Data Provider Process page.
We do not require an NDA, but many data providers have requested for one.
Data provider auditing does not happen unless we suspect that there might be data falsification. For requests, RESET might request for random raw data from monitors to compare with the averaged data submitted to the RESET Cloud in the form of a .csv.
The process takes anywhere from 2 weeks to 2 months. It really just depends on the API connection development. If the API is developed smoothly and connects to the RESET Cloud properly on the first try, then 2 weeks is the best case scenario.
2. Data Provider Requirements
You must demonstrate to RESET that you have a way to display and communicate data to the occupants. There is no required way to show the data.
For certification, you only need to demonstrate that there is a way for occupants to access the data. This could be via an app. A live public display is currently not necessary.
Yes.
That will suffice. Screenshots on how you would display the data to occupants will suffice for submission purposes.
3. API & Data Requirements
You can find the Data Provider API documentation here: https://doc.reset.build/providers/v2/.
Our development team will provide a token for you to communicate with the RESET Cloud servers to test the API.
There are two options: once every 24 hours or once every 30 minutes. Final frequency just means that you have options for how often and when, which would be finalized when implementing the API.
Yes. That fulfills our requirements of 30 minute averaged data submitted at least once every 24 hours.
There are no specific rules other than it must be unique from your data provider platform. We typically recommend to use the UUID of the monitor.
Unfortunately, there is currently no API for checking monitors, but it is probably something we should consider. For now, if you want to create monitors dynamically, the current solution includes the following two ways:
a）Keep an "added monitors" list on your side. A monitor should have been added if you received ‘ack’:’true’ for the monitor create message.
b）Use a redundancy creation strategy since we currently do not have any restrictions around creating a monitor on top of an existing monitor.
a）Keep an "added monitors" list on your side. A monitor should have been added if you received ‘ack’:’true’ for the monitor create message.
b）Use a redundancy creation strategy since we currently do not have any restrictions around creating a monitor on top of an existing monitor.
No, there is currently no way to delete monitors programmatically. If it is necessary, please contact us.
There are currently no limits as to the number of monitors you can create.