Services in Locations

Learn how services should be added to locations.

A Service is an individual utility service an Organisation provides to an end User.

Example:

{
  ...
"services": [
      {
        "id": "7840cdb9-b899-40f6-b9da-9d43a2c3d49f",
        "type": "consumption_trade",
        "status": "active",
        "measurementResolution": "day",
        "measurementId": "bf72c52f-2d2e-4179-bcc1-8ab4718b6e16",
        "costResolution": "day",
        "costId": "a6c4cc79-c1ed-4804-a484-c683ee1e58b0",
        "properties": {
          "showSpotPrice": true,
          "showCost": true,
          "realtimeMeasurements": true
        },
        "startDate": "2023-10-20T15:30:30+02:00",
        "endDate": null
      }
    ]
  ...
}

The services array is embedded in the Get locations response body. All services provided for a single accountId shall be listed with the correct services[i].type. The dependency of this array is visualized in Kit Requests - Sequence Diagram.

The service object includes important id's (all of which should be globally unique) that make it possible to call other API endpoints using the following relationships:

The follow fields determine the smallest time period (resolution) available to request the associated data:

  • measurementResolution
  • costResolution