generated: '2026-07-27'
method: searched
source: >-
  Searched hildebrand.co.uk, glowmarkt.com, data.glowforindustry.com, docs.glowmarkt.com and the
  five Swagger definitions on 2026-07-27 for a versioning policy, deprecation policy, SLA and
  status page. Version facts derived from openapi/*.json info.version and the fixed /api/v0-1 base path.
versioning:
  scheme: uri-path
  current: v0-1
  mechanism: Version segment fixed in the base path — https://api.glowmarkt.com/api/v0-1
  docs: null
  per_system_spec_versions:
    Glowmarkt User System: 1.0.5
    Virtual Entity System: 1.3.0
    Resource System: 1.5.0
    Device Management System: 1.1.0
    Notification System: 1.0.0
  notes: >-
    The path version has been v0-1 since at least the 2018 examples in the official PDF, while each
    system's Swagger info.version advances independently and is not surfaced at runtime. No version
    header, no version-negotiation mechanism, no published version policy. A "/v2/" segment exists
    under the Swagger UI mounts (e.g. /api-docs/v0-1/vesys/v2/) but serves a byte-identical
    definition — an Express static-mount artifact, not a second API version.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecated_operations: []
  notes: >-
    No deprecation or sunset policy is published, no RFC 8594 Sunset/Deprecation header support is
    documented, and no operation in any of the five definitions carries `deprecated: true`. Two
    operations self-describe partial support in prose instead — resource.getMeterRead ("Not
    supported for all resource types") is the clearest example. No `Deprecation` pointer is emitted.
sla:
  url: null
  public_uptime_target: null
  notes: >-
    No public SLA. The only SLA reference found is on the Glow Data Service pricing page, where
    "Custom SLA agreements" is listed as a feature of the top "Dedicated" tier — i.e. SLAs are
    contractual and negotiated, never published.
status_page:
  url: null
  found: false
  probes:
    - {url: 'https://status.glowmarkt.com', result: does not resolve}
    - {url: 'https://status.hildebrand.co.uk', result: does not resolve}
    - {url: 'https://glowmarkt.statuspage.io', result: '200 but serves the Atlassian Statuspage marketing site — no Hildebrand page exists'}
  notes: >-
    No status page, uptime history or incident feed of any kind. Incidents are handled through
    email support (support@glowmarkt.com), the community forum (forum.glowmarkt.com) and — for
    contracted organisations — the Glow Support Portal. No `StatusPage` pointer is emitted.
changelog:
  url: null
  found: false
  notes: >-
    No dated API changelog. The nearest published artefact is the company news feed at
    https://data.glowforindustry.com/articles (product announcements, month-granularity, e.g.
    "Introducing the Glow Agent Portal", June 2026) — wired as `Blog`, not as `ChangeLog`. The
    individual-user PDF carries its own document version and date (v1.8, 09 April 2026) but
    records no per-release API changes.
support_lifecycle:
  channels:
    - {name: Email support, url: 'mailto:support@glowmarkt.com'}
    - {name: Community forum, url: 'https://forum.glowmarkt.com/'}
    - {name: Contact, url: 'https://www.hildebrand.co.uk/contact-us'}
    - {name: Glow Support Portal, url: null, note: 'contract-gated, not publicly reachable'}
  minimum_terms:
    core: 3 months
    enterprise: 1 year
    source: https://data.glowforindustry.com/#pricing