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 Virtual Entity's Metadata API

A Virtual Entity's metadata can be used to save information that will facilitate the virtual representation of the entity. This is typically attribute data that does not change in time.

Hildebrand Virtual Entity’s Metadata API is one of 22 APIs that Hildebrand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Virtual Entity’s Metadata. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 3 operations across 1 path, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 1.3.0.

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

3 operations 1 paths 7 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.3.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 Virtual Entity's Metadata 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 applicationId (userId).

Paths & Operations 3

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

Virtual Entity's Metadata 3

A Virtual Entity's metadata can be used to save information that will facilitate the virtual representation of the entity. This is typically attribute data that does not change in…

GET
/virtualentity/{id}/attribute
Find a Virtual Entity's metadata by ID
virtualentity.getAttributes 1 param → 200401404500
POST
/virtualentity/{id}/attribute
Add/Update a Virtual Entity's metadata
virtualentity.add-updateAttributes 1 param body → 201400500
DELETE
/virtualentity/{id}/attribute
delete metadata from the Virtual Entity
virtualentity.deleteAttributes 1 param body → 200500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are VEResDeletedAttributes (3 properties), GetAtrributesRes (2 properties), VEReqUpdateAttributes (2 properties), reqError (1 property). Each schema is shown below with its type and property counts.

VEReqUpdateAttributes
object
Anything can be added in a ve's metadata
2 properties
AccessDeniedError
object
1 property
VEReqDeleteAttributes
object
Insert the attributes you would like to delete under the field removeAttributes
1 property 1 required
ServerError
object
1 property
GetAtrributesRes
object
2 properties
VEResDeletedAttributes
object
3 properties 2 required
reqError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-virtual-entity-s-metadata-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 API
Hildebrand Device Meter Point DCC inventory API
Hildebrand Device Type API
Hildebrand Discover API
Hildebrand Meter Point Consent & Verification API
Where this information came from

This is an independent, third-party profile of Hildebrand Virtual Entity's Metadata 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.