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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Hildebrand

Glowmarkt Virtual Entity System API

CRUD over Virtual Entities — the Glow Platform's model of a physical "thing" such as a home or a site, made up of metadata and a collection of resources. Lists the virtual entities a caller has access to, resolves the resources belonging to each, manages virtual entity types and metadata attributes, and reports per-application virtual entity statistics.

Documentation Provider Profile APIs.io OpenAPI GitHub

Glowmarkt Virtual Entity 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 Virtual Entities, Sites, Metadata, and Energy Data. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 15 operations across 8 paths, organized into 4 resource areas, and defines 23 schemas. It is described by OpenAPI 2.0, at version 1.3.0.

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

15 operations 8 paths 23 schemas 2 DELETE8 GET3 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 6

Glowmarkt Virtual Entity System API declares 6 security schemes for authenticating requests. 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 (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 15

Across 8 paths, the API surfaces 15 operations — 2 DELETE, 8 GET, 3 POST, 2 PUT. They span 4 resource areas: Virtual Entity Type, Virtual Entity, Virtual Entity's Metadata, Virtual Entity Statistics. Each is listed below with its method, path, parameters, and response codes.

Virtual Entity Type 5

Entity that belongs and is managed by an application and contains the definition and combination of the Resource Types that are required to create a Virtual Entity.

POST
/vetype
Add a new Virtual Entity Type
veType.addVeType 1 param → 201400500
GET
/vetype
Find all Virtual Entity Types
veType.findAll → 200400500
GET
/vetype/{id}
Find Virtual Entity Type by ID
veType.findById 1 param → 200400404500
PUT
/vetype/{id}
Update a Virtual Entity Type
veType.updateVeType 2 params → 201400500
GET
/vetype/{id}/resources
Find all resources that belong to a user that satisfy the Resource Types in the Virtual Entity Type definition.
veType.findResourcesOfVeType 1 param → 200400500
Virtual Entity 6

A Virtual Entity is an instance of the Virtual Entity Type and is tied to an owner as well as an applicationId. In order to create a Virtual Entity a user must have all the requir…

POST
/virtualentity
Add a new Virtual Entity
virtualentity.addVirtualEntity 1 param → 201400500
GET
/virtualentity
Find all Virtual Entities
virtualentity.findAll → 200500
GET
/virtualentity/{id}
Find Virtual Entity by ID
virtualentity.findById 1 param → 200404500
PUT
/virtualentity/{id}
Update a Virtual Entity
virtualentity.updateVirtualEntity 2 params → 201400500
DELETE
/virtualentity/{id}
Delete a Virtual Entity
virtualentity.deactivateVirtualEntity 1 param → 200500
GET
/virtualentity/{id}/resources
Find the resources of that belong to Virtual Entity with ID
virtualentity.findResourcesbyVeId 1 param → 200404500
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 2 params → 201400500
DELETE
/virtualentity/{id}/attribute
delete metadata from the Virtual Entity
virtualentity.deleteAttributes 2 params → 200500
Virtual Entity Statistics 1

APIs that return an overview of the Virtual Entities an application has (administrative API).

GET
/vesys/appstats
find statistics on the number of Virtual Entities per application
stats.getApplicationVeStats → 200400500

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are Resource (10 properties), Ve (8 properties), VeWithFullResources (8 properties), Vedeactive (7 properties). Each schema is shown below with its type and property counts.

newVeTypeReq
object
3 properties
updateVeTypeReq
object
2 properties
reqError
object
1 property
newVeTypeRes
object
2 properties
VeType
object
6 properties
VeTypeResources
object
5 properties
ResourceTypeAvailableResources
object
3 properties
Resource
object
10 properties
VEReq
object
3 properties
VEUpdateReq
object
2 properties
VEReqUpdateAttributes
object
Anything can be added in a ve's metadata
2 properties
VEReqDeleteAttributes
object
Insert the attributes you would like to delete under the field removeAttributes
1 property 1 required
VEResDeletedAttributes
object
3 properties 2 required
Ve
object
8 properties
VeWithFullResources
object
8 properties
GetAtrributesRes
object
2 properties
Vedeactive
object
7 properties
ListOfVeType
array
ListOfVe
array
ServerError
object
1 property
AddVeSucess
object
2 properties
VeStats
object
3 properties
AccessDeniedError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-glowmarkt-virtual-entity-system-swagger.json Raw ↑

Other APIs Hildebrand publishes across the network.

Glowmarkt User System API
AE Profile APIs.io
Glowmarkt Resource System API
AE Profile APIs.io
Glowmarkt Device Management System API
AE Profile APIs.io
Glowmarkt Notification System API
AE Profile APIs.io
#Virtual Entities#Sites#Metadata#Energy Data
← Back to G APIs
API Details
ID
hildebrand:glowmarkt-virtual-entity-system-api
Base URL
https://api.glowmarkt.com/api/v0-1
Docs
https://api.glowmarkt.com/api-docs/v0-1/vesys/
Provider
Hildebrand
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=glowmarkt-virtual-entity-system-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/glowmarkt-virtual-entity-system-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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