generated: '2026-07-27'
method: searched
source: >-
  Live probes of virtual-peaker.com (/status/, /security/, /trust/, /compliance/, /roadmap/ — all
  404; status.virtual-peaker.com and trust.virtual-peaker.com do not resolve), plus the changelog
  and integration-process sections of the two published Gravity Connect guides.
versioning:
  scheme: specification semver + URI major on the publishing host
  current: 2.0.6
  uri_version: /v1 (https://partner.virtualpeaker.io/v1)
  docs: https://assets.virtualpeaker.io/gravity-connect/device-partner-api.html
  note: >-
    The specification version (2.0.6) and the wire version (/v1) move independently: the spec has
    gone 1.0.1 -> 2.0.6 without the publishing path leaving /v1. No version header, no date-based
    versioning, no version negotiation.
deprecation:
  policy_url: null
  policy_published: false
  sunset_header: false
  deprecation_header: false
  note: >-
    No deprecation policy, no sunset schedule, no RFC 8594 Sunset/Deprecation header support and no
    end-of-life commitments are published. The only breakage signal is a changelog line — e.g.
    1.4.0 swapping NORMAL in for RUN_NORMAL and 1.3.3 making `country` required as ISO 3166-1
    alpha-2 — with no notice period stated.
deprecated_operations: []
deprecated_operations_note: >-
  Zero operations across the two OpenAPI documents carry `deprecated: true`.
status_page:
  url: null
  published: false
  probed:
  - {url: 'https://status.virtual-peaker.com/', result: DNS does not resolve}
  - {url: 'https://virtual-peaker.com/status/', status: 404}
  note: >-
    No status page, no uptime history and no incident feed for either partner.virtualpeaker.io or
    the utility/homeowner applications.
sla:
  url: null
  published: false
  uptime_target: null
  note: >-
    No public SLA. Availability commitments, if any, live in the utility contract — this is
    enterprise software sold per program, not a self-serve API.
support:
  knowledge_base: https://support.virtual-peaker.com/knowledge
  api_contact: gravity-connect@virtual-peaker.com
  general_contact: https://virtual-peaker.com/company/contact/
release_process:
  published: false
  integration_stages: [Kickoff Meeting, Onboarding, Implementation, QA, Beta Launch, Go Live]
  note: >-
    The only published lifecycle process is the per-integration one (an OEM's integration goes
    Beta Launch -> Go Live after running smoothly for "a period of time"), not a platform release
    train.
roadmap:
  url: null
  published: false
license:
  spec_license: BSD (declared in info.license of both OpenAPI documents)
  trademark: Gravity Connect API is a registered trademark of Virtual Peaker
  governance: >-
    Vendor-governed. No standards-body home, no public change-control process, no conformance test
    suite and no certification programme.