One of the core design principles of the HAT has been its ability to store any structure data. In v2 of the API this ability was overhauled to simplify data input and minimise setup required before data can be saved.
Therefore, plain Data APIs consume any JSON:
The v2 API loosely replaces the notion of data
table from the previous API version with
namespacesdesignated for it, such as Rumpel only writing to the
rumpelnamespace. Applications are not authorized to write into each other's namespaces
endpointsare defined by the application developer as required. Data is grouped under a combination of a
endpointwhere the two together identify a set of data accessible via a URL path
/api/v2.6/data/namespace/endpoint. An example would be
/api/v2.6/data/rumpel/locationsfor all locations saved into a HAT by the Rumpel app
You will need to acquire an access_token before calling any data APIs. Please refer to the guide on HAT login for details on authentication.