PressureSuite Cloud API daemon example with permanent access token

Purpose:

This example code shows basic access to the PressureSuite Cloud API using an access token from KELLER to gather measurement data from the PressureSuite Cloud. The API's specification can be found here: https://api.pressuresuite.com/swagger/index.html?url=/swagger/v1/swagger.json There is a Python example and a C# example.

Endpoints of interest are:

Endpoint	Use to
GET /v1/Devices	Gets information of all devices
GET /v1/Devices/{deviceId}	Gets information of a specific device
GET /v1/Measurements	Gets a list of measurements composed of a value and a UTC datetime

Needs:

• For the Python example:

  • Python 3.7
  • requests

• For the C# example:

  • .NET Core 3.1 runtime (https://dotnet.microsoft.com/download/dotnet-core/3.1)

It is necessary to have a valid permanent ACCESS_TOKEN Please ask KELLER AG (pressuresuite@keller-druck.com) or your KELLER sales contact to provide a valid permanent ACCESS_TOKEN key

Notes:

DateTime format from the API is always in UTC
Pressure values from the API are always in bar
Temperature values from the API are always in °C
It is not possible to delete measurement data with the API

If you want to try out the API with Swagger press the dark green [Authorize] button and a valid bearer token. You can get a valid bearer token when logged in at https://www.pressuresuite.com under [User Settings].
The deviceIds are the same numbers that can be seen in the URL of the WebApp when the device is selected: https://www.pressuresuite.com/devices/1234/

If you want a permanent ACCESS_TOKEN, please contact the PressureSuite support team (pressuresuite@keller-druck.com). The provided access token must be the value with the key "userOid" in the header of every request.

If you plan run this as a server script to store measurement data from the PressureSuite Cloud API the following procedure is recommended:

• Decide for a time span to gather date: eg. Every 24h
• Create a list of the deviceIds that needs to be monitored (eg. my_devices=[1234,1235,1236])
• Create a list of MeasurementsDefinitonIds representing the physical measurement channel (eg. channels_of_interest=[2,5,7,8,11])
• Run the program every ~24h and
  • for all devices of interest...
  • for all channels of interest..
  • use get_data_measurements_from_timespan() with he timespan of ~24
  • and store the data into a DB
  • you might check first if the measurement(value+timestamp) is not already stored
• It is possible that a request fails. To solve this error case please re-call the data later again. You might gather data from an overlapped time slot and exclude measurements that have been stored already.

Please create GitHub issues for feature wishes or problems.
Or contact pressuresuite@keller-druck.com

Further documentation

Please visit https://docs.pressuresuite.com/cloud-interfaces/api/channels/

FAQ: How do I get calculated data from the API?

Currently, we do not offer calculated data such as “water levels”, “tank levels” etc through the API.

Besides technical and security reasons:

• We believe it will cause more trouble for customers to have this option activated. You can continuously fetch measurements from the Cloud API and automatically store it in the customers DB/system. Now, when anyone (you, another authorized user, your customer) who has write-access changes the calculation settings on the Cloud web page the calculated values will change, too. This might happen by accident and the API starts to deliver false calculation values.
• We from KELLER try to deliver you the rawest measurement data we get from our sensors and believe that when you integrate them into a customer’s system then you have to manage and guarantee the calculation, too.

The water calculation itself is not that complicated. You can see the formula in the Cloud web app.