Glow Platform
    • Welcome to Glow Data Service!
    • Getting Started
    • Glow Portals
    • Introducing the Glow System
    • API Authentication
    • Smart Meter Onboarding
      • Introducing Smart Meter Onboarding
      • Smart Meter Eligibility Check
      • Terms and Conditions APIs and Management
      • Onboarding Methods — Direct Integration
        • EUI/Postcode Check
        • AVS Check
      • Onboarding Methods — Hosted Integration
        • Glow IDV SDK
          • Introducing the Glow SDK
          • Supported Verification Methods
          • Implementation Guide — Web
          • Implementation Guide — Mobile
          • Verifiable Credentials
          • Verification Result Screen
          • Consent Capture & Onboarding
      • Onboarding Methods — No Integration
        • Invitation Functionality
        • Agent Verification Portal
    • Data Retrieval
      • Retrieving Time Series Data from Onboarded Users
    • Consent Management and Offboarding
      • Consent Management
      • Offboarding
    • Glow CADs & Fulfilment
      • Glow CAD Fulfilment
    • API Reference
      • Smart Meter Elgibility
        • eligibility
          • smets-ihd-cad
            • Check MPxN has CAD/PPMID
          • checksmetsihd
            • postcode
              • Match EUI IHD with postcode
            • Match EUI IHD with MPxN
          • checksmetsmpxn
            • Check MPXN is eligible in DCC.
      • Content System
        • content
          • {contentId}
            • get a content object
            • Update an existing content object
          • Find all the content objects of an application
          • Add a content object
        • languagecontent
          • {languageContentId}
            • get a language content object by ID
            • Update an existing language content object
          • Find all the language content objects of an application
          • Add a language content object
        • termsconditions
          • {tcId}
            • get a terms and conditions object by ID
          • current
            • Find the terms and conditions that are in force.
          • Find all the terms and conditions of an application
          • Add terms and conditions
        • termsconditionsuser
          • {tcUserId}
            • get a specified terms and conditions user obj
          • Find all the responses to terms and conditions documents.
          • Add a user's response to Terms & Conditions document
        • supportdetails
          • {supportDetailsId}
            • get a support details object
          • Find all the support detail objects of an application
          • Add a support details object
        • faq
          • {faqId}
            • get a FAQ object
          • Find all the FAQ objects of an application
          • Add a faq object
        • prompttype
          • {promptTypeId}
            • get a Prompt Type object
          • Find all the prompt type objects of an application
          • Add a Prompt Type object
        • prompt
          • {promptId}
            • get a Prompt object
          • Find all the prompt objects of an application
          • Add a Prompt object
        • promptuser
          • {promptUserId}
            • get a Prompt User object
          • Find all the prompt user objects of an application
          • Add a Prompt User object
        • useraction
          • {userActionId}
            • get a User Action object
          • Find all the user action objects of an application
          • Add a User Action object
        • useractiontype
          • {userActionTypeId}
            • get a User Action Type object
          • Find all the user action type objects of an application
          • Add a User Action Type object
      • User System
        • register
          • User self registers
        • account
          • {accountId}
            • status
              • Find the status of a specified account. If the account is using an external directory service, this call will confirm whether the user is authenticated against it. This call requires administrative application level credentials.
            • mobileapptoken
              • Add mobile app token to a user
              • Remove a mobile app token to a user
            • Find specific account of an application.
            • Updates the account's metadata.
            • Delete account
          • status
            • With a given JWT token a user can have their account status verfied. If their account is created under an external directory service, this call will establish whether a user's token to the external service is still valid.
          • email
            • Change a user's email
          • name
            • Change a user's name
          • changepassword
            • Change a user's password
          • Find all accounts of an application
          • Add an account to an existing user
        • user
          • {userId}
            • username
              • Change a user's username
            • Find specific user that has an account in an application.
            • Delete specific user. This will delete all the accounts of a user. Please refer to delete account API. This API requires specific permissions.
          • verify
            • Generate a user verification token
            • Verify a user verification token
          • resetpassword
            • Generate a token that can be used by user to reset their password.
            • A user resets their password
          • verification
            • status
              • mpxns
                • renewal
                  • Renew consent for a number of meterpoints
                • revocation
                  • Revoke consent for a number of meterpoints
              • mpxn
                • {mpxn}
                  • renewal
                    • Get meter point consent renewals
                    • Renew meter point consent
                  • revocation
                    • Get meter point consent revocations
                    • Revoke meter point consent
              • API to retrieve user's meter points' consent and verification
          • Find specific user that has an account in an application from the username.
          • Create a user
        • accountprofile
          • {profileName}
            • Find specific group of application
          • Find all the profiles of an account
          • Create an account profile under a given profileName.
        • accountsession
          • get the session of an account
          • Update an account session.
        • auth
          • token
            • {tokenId}
              • Deletes a token, specified by its tokenId.
            • Returns all the tokens that are active and valid for a specified user.
          • newToken
            • Generate a new token for an account.
          • deleteToken
            • delete a token
          • oauth
            • access
              • Exchange the Authorization Code for an Access Token.
            • Check and validate an Oauth Access token.
            • Authenticate a user and generate an OAuth 2.0 Authorization Code Grant.
          • Checks whether a user token is valid.
          • authenticate an account
      • Virtual Entity System
        • vesys
          • appstats
            • find statistics on the number of Virtual Entities per application
        • virtualentity
          • {id}
            • resources
              • Find the resources of that belong to Virtual Entity with ID
            • attribute
              • Find a Virtual Entity's metadata by ID
              • Add/Update a Virtual Entity's metadata
              • delete metadata from the Virtual Entity
            • Find Virtual Entity by ID
            • Update a Virtual Entity
            • Delete a Virtual Entity
          • Add a new Virtual Entity
          • Find all Virtual Entities
        • vetype
          • {id}
            • resources
              • Find all resources that belong to a user that satisfy the Resource Types in the Virtual Entity Type definition.
            • Find Virtual Entity Type by ID
            • Update a Virtual Entity Type
          • Add a new Virtual Entity Type
          • Find all Virtual Entity Types
      • Webhook System
        • webhook
          • {webhookId}
            • Find webhook by ID
          • error
            • {errorId}
              • Find a particular webhook error
            • Find all the webhooks that have failed
          • Find all webhooks of an application (or user)
      • Resource System
        • resource
          • {id}
            • readings
              • Get resource readings
            • current
              • Get the current resource reading.
            • first-time
              • Get the UTC time of the first available reading
            • last-time
              • Get the UTC time of the most recent available reading
            • meterread
              • Get the cumulative value reported on a metering device. (Not supported for all resource types).
            • tariff
              • Get the latest tariff that is being applied to a resource.
            • tariff-list
              • Get the tariff history that is being applied to a cost resource.
            • catchup
              • Trigger a request to retrieve the latest available readings from the DCC.
            • glowbinary
              • API that returns the resource's raw data in the Glow Binary format.
            • Find resource by ID
          • count
            • Count the number of resources per resourceType
          • Add a new resource
          • Find all resources per user or application
        • resourcetype
          • {id}
            • resource
              • Find resources of a specific resource type that belong to a user
            • appresource
              • Find resources of a specific resource type that an application has access to
            • Find resourceType by ID
          • Add a new resource type.
          • Find all resource types
      • Notification System
        • alerttype
          • {alertTypeId}
            • Find alert type by ID
            • Updates the alert type's metadata.
          • Find all alert types of an application
          • Create an alert type
        • alert
          • {alertId}
            • Get an alert by Id
          • user
            • Get the alerts sent to a user
          • Send an alert
        • template
          • {templateId}
            • Find template type by ID
            • Updates the teplate's metadata.
          • {alertTypeId}
            • {channelType}
              • {cultureCode}
                • Find template by alertTypeId, channeType and cultureCode
                • Create template by alertTypeId, channeType and cultureCode
          • Find all templates of an application
          • Create a template
        • notification
          • {notificationId}
            • log
              • Get the logs of a particular notification
            • Get a notification by Id
      • DFS
        • dfs
          • termsconditions
            • The current version of terms and conditions that is pertinent to DFS for a particular application.
          • user
            • Get all the users that have opted in the DFS functionality
            • User opts in to DFS functionality for a particular MPxN. The mpxn field is only required if a user has more than one MPxN.
            • User opts out of DFS functionality
          • event
            • {dfsEventId}
              • user
                • Get all the users that have participated in a particular DFS event
            • user
              • participation
                • API to indicate User participating in particular DFS event
              • Get all the events a user has signed up for
      • Device Management System
        • devicetype
          • {id}
            • Find Device Type by ID
          • Add a new Device Type
          • Find all device types
        • device
          • {id}
            • status
              • This call can be used to see whether a gateway device is sending packets to the Glow Platform (i.e. via WiFi).
            • Find device by ID
          • resource
            • {resourceId}
              • Find the device that sources a specified resource.
          • meter-point
            • {meterPointNumber}
              • inventory
                • Get the DCC inventory of a meter point
              • resources
                • Get the resources associated to a meter point
          • smart-meter
            • {eui}
              • inventory
                • Get the DCC inventory of a meter point by providing an EUI.
          • status
            • This call can be used to see whether a gateway device is sending packets to the Glow Platform (i.e. via WiFi).
          • Get a user's devices
          • Add a new device
        • discover
          • {hardwareId}
            • Find device by ID

    Getting Started

    From completing the sign up process to accessing data for your energy consumers, we've put together this guide on how to set up your organisation with our Glow Data Service.

    Part One: Starting your subscription#

    Login to your account#

    Get started by logging into your account.
    If you have not created an account yet, you can register here.
    Currently, the automated sign up process for Glow Data Service is only available for our SME tier. If you are interested in our Enterprise or Dedicated plans, please contact us directly.

    Create your first application#

    To use Glow Data Service, you must first create an application. All the energy consumers you onboard have to exist within an application. If you're running different projects or managing different groups of energy consumers, you can create multiple applications.
    There are four steps to creating an application:
    1
    Fill out your application name, description and purpose
    We also ask for your organisation's public privacy policy. If you do not have one, please contact support@glownetzero.com.
    2
    Provide contact details
    Part of setting up your organisation with Glow Data Service includes creating accounts in the Glow Support and Development portals for the relevant memebrs of your organisation. We capture their contact details now so they're set up as soon as your application is live.
    At this stage, we also capture details for the Data Protection Officer at your organisation. This person will be added to the generated legal agreement and are tasked with ensuring GDPR compliance.
    3
    Choose verification methods
    Will you be integrating Glow Data Service into your own front end, or using existing Glow applications to complete energy consumer verification and capture consent? Here, we ask which of our multiple verification methods you plan to use.
    4
    Review information and generate contract
    Once you have filled in all the required details, the final step is to review what you've provided and generate a Master Services Agreement.
    Upon generating your Agreement, we will email you a copy of our Master Services Agreement tailored to your organisation. In parallel, we store the details of your application submission and your application will be added to the Dashboard in your account, with a status of pending.
    Once the Agreement has been reviewed and signed by all parties, the Glow team will finalise your application and put it live.

    Review and sign agreement#

    You will be emailed a copy of our Master Services Agreement to review, populated with your organisation's details. The agreement must be signed by your organisation, Hildebrand and by the Glow team.
    A copy of the fully signed Agreement will be sent to you for your records and is visible in your organisation's Dashboard.

    Part Two: Accessing Glow Data Service#

    Once all parties have signed the Agreement, your Glow Data Service subscription will officially begin and the Glow team will put your application live.
    This may take 1-2 working days, and the team will contact you with any questions or additional required information. You will not enter the billing period until your application is live.

    Support and Development portals#

    With a live application, you will gain access to our Glow Support and Development portals. For more detail on these portals, please visit our page here.

    Onboard energy consumers#

    A live application means you can start onboarding your energy consumers. As smart meter data is highly regulated, specific protocols for verifying energy consumers and capturing their explicit consent for data to be accessed must be followed.
    Glow offers multiple approved methods for verification and consent, which were outlined for you at the time of creating an application. Some of these methods can be integrated into your own front end, while others rely on our own Glow applications and thus no integration is required.
    Please visit our Smart Meter Onboarding section for a full introduction to energy consumer onboarding via Glow, and for user guides each onboarding method.

    Access data#

    With your energy consumers successfully onboarded, you can start retrieving their energy data.
    Our tutorial for accessing time series data via the Glow APIs is found here.

    Add new applications (optional)#

    If you'd like to add additional applications, you can do so from your Dashboard on the Glow Data Service site when you are signed in as your organisation.
    The process is the same as creating your first application though a few less details are required. You will also not need to generate another Agreement, though depending on the verification methods selected, addendums to your existing Agreement may be required.

    Part Three: Managing your subscription#

    Billing and invoicing#

    When your first application goes live, you will enter the billing period and receive your first invoice for the service soonafter. Invoices are sent quarterly in advance for the service fee, with additional charges per MPxN over the minimum, if applicable.
    The full terms of billing for the Data Service are found in the Master Services Agreement.

    Cancellation#

    You can cancel your Glow Data Service at any point, but a two months notice period is required. To do so, please contact the Glow team directly and we'll follow up with next steps.
    The minimum term for the service is three months (the two month notice period is included in this minimum term).

    Support#

    If you have any further questions or require clarification on using the Service, please contact the Glow team at support@glownetzero.com.
    Modified at 2026-08-25 11:37:53
    Previous
    Welcome to Glow Data Service!
    Next
    Glow Portals
    Built with