How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Glowmarkt User System API

User, account, authentication and consent management for the Glow Platform. Covers user registration, account profiles and sessions, JWT issuance via POST /auth, an OAuth 2.0 authorization-code grant (POST /auth/oauth and POST /auth/oauth/access), and — the part that matters most in the British smart-metering context — Meter Point Consent and Verification, where consent to retrieve data is renewed and revoked per MPxN.

Glowmarkt User System API is one of 5 APIs that Hildebrand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User, Account, Authentication, Consent, and Meter Points. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 43 operations across 29 paths, organized into 9 resource areas, and defines 44 schemas. It is described by OpenAPI 2.0, at version 1.0.5.

Requests are made against the base URL https://api.glowmarkt.com/api/v0-1.

43 operations 29 paths 44 schemas 4 DELETE16 GET17 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 2.0
API Version
1.0.5
Base URL
https://api.glowmarkt.com/api/v0-1
Authentication
API Key, basic, basic, API Key, API Key, API Key, API Key, API Key, API Key
License
Copyright © 2012-26 by Hildebrand Technology Limited
Resource Areas
9

Authentication & Security 9

Glowmarkt User System API declares 9 security schemes for authenticating requests. An API key is passed in the header as token (oAccessAuthToken). It defines a basic scheme (orgAppKeys). It defines a basic scheme (appKeys). An API key is passed in the header as token (devUserToken). An API key is passed in the header as token (internalUserToken). An API key is passed in the header as token (userToken). An API key is passed in the header as applicationId (applicationId). An API key is passed in the header as userId (userId). An API key is passed in the header as organizationId (organizationId).

Paths & Operations 43

Across 29 paths, the API surfaces 43 operations — 4 DELETE, 16 GET, 17 POST, 6 PUT. They span 9 resource areas: User, Account, Account Profile, Account Session, accountsession, Auth, auth, OAuth, Meter Point Consent & Verification. Each is listed below with its method, path, parameters, and response codes.

User 10
POST
/register
Create a user
addUser 1 param → 200400401500
GET
/user
Find specific user that has an account in an application from the username.
getUserbyUsername 1 param → 200401404500
POST
/user
Create a user
createUser 1 param → 200400401500
GET
/user/{userId}
Find specific user that has an account in an application.
getUserbyId 1 param → 200401404500
DELETE
/user/{userId}
Delete specific user. This will delete all the accounts of a user. Please refer to delete account API. This API requires specific permissions.
deleteUserbyId 1 param → 200401404500
POST
/user/verify
Generate a user verification token
generateUserVerificationToken 1 param → 200400401500
PUT
/user/verify
Verify a user verification token
verifyUser 1 param → 200400401500
POST
/user/resetpassword
Generate a token that can be used by user to reset their password.
generateUserPasswordResetToken 1 param → 200400401500
PUT
/user/resetpassword
A user resets their password
resetPasswordUser 1 param → 200400401500
PUT
/user/{userId}/username
Change a user's username
updateUsernameUserId 2 params → 200400401500
Account 12
GET
/account
Find all accounts of an application
getAccounts → 200401500
POST
/account
Add an account to an existing user
addAccount 1 param → 200400401500
GET
/account/{accountId}
Find specific account of an application.
getAccountbyId 1 param → 200401404500
PUT
/account/{accountId}
Updates the account's metadata.
updateAccount 2 params → 200400401500
DELETE
/account/{accountId}
Delete account
deleteAccount 1 param → 200400401500
GET
/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 a…
getAccountStatusbyId 1 param → 200401404500
GET
/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 s…
getAccountStatusbyUserToken → 200401404500
POST
/account/email
Change a user's email
userChangeEmail 1 param → 200400401500
POST
/account/name
Change a user's name
userChangeName 1 param → 200400401500
POST
/account/changepassword
Change a user's password
userChangePassWord 1 param → 200400401500
POST
/account/{accountId}/mobileapptoken
Add mobile app token to a user
2 params → 200401500
PUT
/account/{accountId}/mobileapptoken
Remove a mobile app token to a user
2 params → 200401500
Account Profile 3
GET
/accountprofile
Find all the profiles of an account
getAccountProfile → 200401500
POST
/accountprofile
Create an account profile under a given profileName.
addAccountProfile 1 param → 200400401500
GET
/accountprofile/{profileName}
Find specific group of application
getAccountProfilebyProfileName 1 param → 200401404500
Account Session 1
GET
/accountsession
get the session of an account
getAccountSession → 200401500
accountsession 1
PUT
/accountsession
Update an account session.
updateAccountSession 1 param → 200400401500
Auth 1
GET
/auth
Checks whether a user token is valid.
tokencheck → 200400500
auth 5
POST
/auth
authenticate an account
usernamelogin 2 params → 200400401500
GET
/auth/token
Returns all the tokens that are active and valid for a specified user.
getTokenOfUser → 200400500
DELETE
/auth/token/{tokenId}
Deletes a token, specified by its tokenId.
deleteTokenById 1 param → 200400500
GET
/auth/newToken
Generate a new token for an account.
newToken → 200400500
DELETE
/auth/deleteToken
delete a token
deleteToken → 200400401500
OAuth 3
GET
/auth/oauth
Check and validate an Oauth Access token.
validateOAuthAccessToken → 200400401500
POST
/auth/oauth
Authenticate a user and generate an OAuth 2.0 Authorization Code Grant.
generateOAuthorizationCode 2 params → 200400401500
POST
/auth/oauth/access
Exchange the Authorization Code for an Access Token.
exchangeAuthorizationCodeWithAccess 1 param → 200400401500
Meter Point Consent & Verification 7
GET
/user/verification/status
API to retrieve user's meter points' consent and verification
getUserMeterPointVerificationConsentStatus → 200400401500
POST
/user/verification/status/mpxns/renewal
Renew consent for a number of meterpoints
renewMeterPointConsentBulk 1 param → 200400401500
POST
/user/verification/status/mpxns/revocation
Revoke consent for a number of meterpoints
renewMeterPointConsentRevokeBulk 1 param → 200400401500
GET
/user/verification/status/mpxn/{mpxn}/renewal
Get meter point consent renewals
getMeterPointConsentRenewal 1 param → 200400401500
POST
/user/verification/status/mpxn/{mpxn}/renewal
Renew meter point consent
renewMeterPointConsent 2 params → 200400401500
GET
/user/verification/status/mpxn/{mpxn}/revocation
Get meter point consent revocations
getMeterPointConsentRevocation 1 param → 200400401500
POST
/user/verification/status/mpxn/{mpxn}/revocation
Revoke meter point consent
revokeMeterPointConsent 2 params → 200400401500

Schemas 44

The contract defines 44 schemas that model the data the API accepts and returns. The most detailed are UpdateAccountRes (11 properties), AccountRes (11 properties), AccountStatus (8 properties), TokenDocument (6 properties). Each schema is shown below with its type and property counts.

TokenDocument
object
6 properties
RenewMeterPointConsentReq
object
1 property
RevokeMeterPointConsentReq
object
1 property
MeterPointConsentAndVerification
object
4 properties
MeterPointConsentAndVerificationRenewal
object
6 properties
MeterPointConsentAndVerificationRenewalRes
object
2 properties
MeterPointConsentAndVerificationRevocation
object
6 properties
MeterPointConsentAndVerificationRevocationRes
object
2 properties
MpxnElem
object
1 property
MeterPointVerificationRenewalElem
object
4 properties
MeterPointVerificationRevocationElem
object
4 properties
MeterPointConsentManagementBulkReq
object
1 property
MeterPointConsentManagementBulkRenewalRes
object
2 properties
MeterPointConsentManagementBulkRevocationRes
object
2 properties
UserMeterPointConsentAndVerification
object
1 property
AddUserReq
object
6 properties 6 required
AddUserRes
object
6 properties
CreateUserRes
object
6 properties
AccountRes
object
11 properties
AccountStatus
object
8 properties
AddAccountReq
object
2 properties 2 required
CreateUserReq
object
2 properties 2 required
UserChangeUsernameAdminBodyReq
object
2 properties
UpdateAccountRes
object
11 properties
AccountProfile
object
2 properties 1 required
AccountSession
object
2 properties
GenerateVerificationTokenUserReq
object
3 properties 3 required
VerifyUserReq
object
4 properties 4 required
GeneratePasswordResetTokenUserReq
object
2 properties 2 required
PasswordResetUserReq
object
4 properties 4 required
AddMobileTokenToAccountReq
object
1 property 1 required
RemoveMobileTokenToAccountReq
object
1 property 1 required
UserNameLoginReq
object
3 properties 2 required
OAuthValidAccessToken
object
2 properties
OAuthCodeRes
object
5 properties
OAuthAccessRefreshToken
object
4 properties
ExchangeAuthorizationCodeWithAccessRes
object
4 properties
IsValidRes
object
1 property
Error
object
1 property
AccessDeniedError
object
1 property
InternalServerError
object
1 property
IncorrectElementsError
object
1 property
MissingElementsError
object
1 property
ApiResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-glowmarkt-user-system-swagger.json Raw ↑

Other APIs Hildebrand publishes across the network.

Glowmarkt Resource System API
Glowmarkt Virtual Entity System API
Glowmarkt Device Management System API
Glowmarkt Notification System API
Where this information came from

This is an independent, third-party profile of Glowmarkt User System API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.