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 Device API

The Device API from Hildebrand — 5 operation(s) for device.

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

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

This API exposes 6 operations across 5 paths, and defines 8 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

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

6 operations 5 paths 8 schemas 5 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 6

Hildebrand Device API declares 6 security schemes for authenticating requests. 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 (userToken). An API key is passed in the header as applicationId (applicationId). An API key is passed in the header as userId (userId).

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 5 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Device 6
GET
/device
Get a user's devices
device.findAll 1 param → 200400404500
POST
/device
Add a new device
device.addDevice body → 200400500
GET
/device/{id}
Find device by ID
device.findById 1 param → 200404500
GET
/device/resource/{resourceId}
Find the device that sources a specified resource.
device.findByResourceId 1 param → 200404500
GET
/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).
device.getStatusbyDeviceId 1 param → 200400500
GET
/device/status
This call can be used to see whether a gateway device is sending packets to the Glow Platform (i.e. via WiFi).
device.getStatusbyHardwareId 1 param → 200400500

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are Device (8 properties), DeviceReq (3 properties), AddDeviceSuccess (3 properties), ProtocolResourceTypeResource (3 properties). Each schema is shown below with its type and property counts.

ProtocolResourceTypeResource
object
3 properties 3 required
ParentHardwareIds
string
DeviceReq
object
3 properties 3 required
Device
object
8 properties 2 required
missingUserIdError
object
1 property
AddDeviceSuccess
object
3 properties
ServerError
object
1 property
IncorrectElementsError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-device-api-openapi.yml Raw ↑

Other APIs Hildebrand publishes across the network.

Hildebrand Account API
Hildebrand Account Profile API
Hildebrand Account Session API
Hildebrand Accountsession API
Hildebrand Alert API
Hildebrand Alerttype API
Hildebrand Auth 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 Device 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.