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

Hildebrand Account API

The Account API from Hildebrand — 8 operation(s) for account.

Hildebrand Account API is one of 22 APIs that Hildebrand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 12 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.5.

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

12 operations 8 paths 10 schemas 1 DELETE4 GET5 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 9

Hildebrand Account API declares 9 security schemes for authenticating requests. An API key is passed in the header as token (oAccessAuthToken). It accepts HTTP basic authentication (orgAppKeys). It accepts HTTP basic authentication (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 12

Across 8 paths, the API surfaces 12 operations — 1 DELETE, 4 GET, 5 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Account 12
GET
/account
Find all accounts of an application
getAccounts → 200401500
POST
/account
Add an account to an existing user
addAccount body → 200400401500
GET
/account/{accountId}
Find specific account of an application.
getAccountbyId 1 param → 200401404500
PUT
/account/{accountId}
Updates the account's metadata.
updateAccount 1 param body → 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 body → 200400401500
POST
/account/name
Change a user's name
userChangeName body → 200400401500
POST
/account/changepassword
Change a user's password
userChangePassWord body → 200400401500
POST
/account/{accountId}/mobileapptoken
Add mobile app token to a user
1 param body → 200401500
PUT
/account/{accountId}/mobileapptoken
Remove a mobile app token to a user
1 param body → 200401500

Schemas 10

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

InternalServerError
object
1 property
AddMobileTokenToAccountReq
object
1 property 1 required
AccessDeniedError
object
1 property
IncorrectElementsError
object
1 property
AddAccountReq
object
2 properties 2 required
AccountRes
object
11 properties
UpdateAccountRes
object
11 properties
MissingElementsError
object
1 property
RemoveMobileTokenToAccountReq
object
1 property 1 required
AccountStatus
object
8 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-account-api-openapi.yml Raw ↑

Other APIs Hildebrand publishes across the network.

Hildebrand Account Profile API
Hildebrand Account Session API
Hildebrand Accountsession API
Hildebrand Alert API
Hildebrand Alerttype API
Hildebrand Auth API
Hildebrand Device API
Hildebrand Device Meter Point DCC inventory API
Hildebrand Device Type API
Hildebrand Discover API
Hildebrand Meter Point Consent & Verification API
Hildebrand Notification API
Where this information came from

This is an independent, third-party profile of Hildebrand Account 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.