Updates

2025-12-10

• Both aggregations and aggregation are accepted as query parameter name for the /statistics endpoint. Previously, only aggregations was accepted, and using for example aggregation=count would not be recognised as the query parameter, and the API would return the default aggregation of avg instead.

2025-12-09

• All three endpoints /metadata, /measurements and /statistics now accept a verbose query parameter. This is a flag to toggle on verbose domainIds. Some domains offer more human-friendly, verbose domainIds; if verbose is set to true, the domainIds in the response will be verbose. Below is an example of a verbose versus regular domainId within the vis-3-8a domain:

  • regular: IMO1234567/411.1/C101.31-6/meta/qty-temperature/cnt-coolant/pos-outlet

  • verbose: IMO1234567/411.1/C101.31-6/~propulsion.engine/~cylinder.6/meta/qty-temperature/cnt-coolant/pos-outlet

2025-11-19

• Added general support for the vis-3-8a domain. Queries can now be done using vis-3-8a domainIds, see the relevant section in the docs here: vis 3-8a domain. Note that the availability of domainIds is subject to time series contextualization, which happens independent of the API development.

2025-11-17

• POSTrequests for /measurements and /statistics using the JSMEA domain now support tags with empty hierarchy levels within the POST body.

• POST requests without the Content-Type header now return a more appropriate Unsupported Media Type error message. application/json is the only allowed value for the header.

2025-11-06

• The mapsTo field in the response to /metadata now contains maker domainIds.