Introducing the Glow System
This page outlines the Glow system from an organisation perspective and defines the relevant components for the Glow APIs.Figure 1 The Glow system, for organisations.
This diagram explains the structure of the core components of the Glow system for smart meter data management; the unique identifiers listed are described in the next section and are core to data retrieval via the Glow APIs.Important: a User is an entity with an account, they can be domestic or smaller non-domestic. The User may not have been through the steps to Verify their DCC enrolled smart meters (verificaton is described later in this document). ONLY when the user has successfully verified their smart meters and granted consent for their data to be retrieved with Virtual Entities and Resources be created.An Organisation can have one or more Applications; organisations can create Applications from the Admin dashboard on the Data Service site. Applications can be used for different front-end applications, or to group users for different projects. The intention is to give the organisation flexibility on how it manages sets of users.Each application will be made up of a number of users (there are no limits to the number of users within an application). Once a user has verified their meters and given consent for the organisation to access data for their property, they will have at least one virtual entity associated to their accounts, which can hold any number of resources depending on the commissioned devices enrolled in the DCC at the property.The Glow APIs are based on the following Objects:| Object | Description | Unique Identifier | API Definition |
|---|
| Organisation | A third-party using Glow Data Service to access data for their own energy consumers. They have a contractual relationship with Hildebrand (the legal entity that powers the Glow platform). | organizationId | https://api.glowmarkt.com/api-docs/v0-1/usersys/orgelements/#/ |
| Application | Exists within an organisation, and is used to group and manage energy consumers. An organisation can have multiple applications. | applicationId | https://api.glowmarkt.com/api-docs/v0-1/usersys/orgelements/#/ |
| User | An energy consumer with an affiliated account that has been onboarded in the Glow system. Each user exists within at least one application and can exist in multiple applications. | userId | https://api.glowmarkt.com/api-docs/v0-1/usersys/usertypes/#/ |
| Virtual Entity | The virtual representation of a physical “thing” that is comprised of metadata and a collection of resources that define and describe it.
An example of a Virtual Entity is a home with electricity and gas energy readings sourced from a smart meter. | veId | https://api.glowmarkt.com/api-docs/v0-1/vesys/#/ |
| Resource | A representation of the data collected from a physical device, including but not limited to an electricity or gas meter, or an installed multisensor. | resourceId | https://api.glowmarkt.com/api-docs/v0-1/resourcesys/#/ |
| Device | The physical hardware that can be either: - a gateway: makes information available to the Glow Platform. The Glow Display/CAD and Glow Delta CAD are examples of Glow gateways.
- a sensor: detects events or changes to its environment and sends information to other devices (such as a smart electricity meter).
- an actuator: a controller, given specific predefined commands it can trigger events, change its environment or perform an operation (auxiliary load control switch in an electricity meter).
| deviceId | https://api.glowmarkt.com/api-docs/v0-1/dmssys/#/ |
Modified at 2026-08-17 10:15:00
