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 Meter Point Consent & Verification API

The Meter Point Consent & Verification API from Hildebrand — 5 operation(s) for meter point consent & verification.

Hildebrand Meter Point Consent & Verification API is one of 22 APIs that Hildebrand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Meter Point Consent & Verification. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 7 operations across 5 paths, and defines 14 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/.

7 operations 5 paths 14 schemas 3 GET4 POST

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 Meter Point Consent & Verification 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 7

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

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 body → 200400401500
POST
/user/verification/status/mpxns/revocation
Revoke consent for a number of meterpoints
renewMeterPointConsentRevokeBulk body → 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 1 param body → 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 1 param body → 200400401500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are MeterPointConsentAndVerificationRenewal (6 properties), AddUserRes (6 properties), MeterPointVerificationRenewalElem (4 properties), MeterPointConsentAndVerification (4 properties). Each schema is shown below with its type and property counts.

MeterPointConsentAndVerificationRenewal
object
6 properties
UserMeterPointConsentAndVerification
object
1 property
InternalServerError
object
1 property
AccessDeniedError
object
1 property
MeterPointVerificationRenewalElem
object
4 properties
MpxnElem
object
1 property
MeterPointConsentAndVerificationRenewalRes
object
2 properties
MeterPointConsentAndVerification
object
4 properties
RenewMeterPointConsentReq
object
1 property
AddUserRes
object
6 properties
MeterPointConsentManagementBulkRevocationRes
object
2 properties
MissingElementsError
object
1 property
MeterPointConsentManagementBulkRenewalRes
object
2 properties
MeterPointConsentManagementBulkReq
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hildebrand-meter-point-consent-verification-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 Notification API
Where this information came from

This is an independent, third-party profile of Hildebrand Meter Point Consent & Verification 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.