The Mobility House

ChargePilot VDV 463 Interface

Two-way WebSocket-Secure interface between ChargePilot (acting as the Charging Management System, CMS) and an upstream Depot Management, Fleet Management or ITCS system, implemented against the VDV 463 standard published by the Verband Deutscher Verkehrsunternehmen. ChargePilot pushes ProvideChargingInformation.req messages carrying a DepotInfoList (depot setup, charging station and charging point statuses, live charging processes, fault information) every 15 seconds; the upstream system may optionally push ProvideChargingRequests.req messages carrying per-vehicle charging schedules. The session opens with a WebSocket TLS handshake authenticated with HTTP Basic credentials issued by The Mobility House, followed by a BootNotification.req/.conf exchange.

GitHub

Documentation

📖
Documentation
https://vdv-docs.tmh.energy/
📖
GettingStarted
https://vdv-docs.tmh.energy/initial-connection/initial-connection/
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/authentication/the-mobility-house-authentication.yml

Other Resources

🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/errors/the-mobility-house-problem-types.yml
🔗
DataModel
https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/data-model/the-mobility-house-data-model.yml
🔗
Conformance
https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/conformance/the-mobility-house-conformance.yml
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/the-mobility-house/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/the-mobility-house-chargepilot-vdv-463"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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

API entry from apis.yml

apis.yml Raw ↑ 
aid: the-mobility-house-chargepilot-vdv-463
name: ChargePilot VDV 463 Interface
description: Two-way WebSocket-Secure interface between ChargePilot (acting as the Charging Management
  System, CMS) and an upstream Depot Management, Fleet Management or ITCS system, implemented against
  the VDV 463 standard published by the Verband Deutscher Verkehrsunternehmen. ChargePilot pushes ProvideChargingInformation.req
  messages carrying a DepotInfoList (depot setup, charging station and charging point statuses, live charging
  processes, fault information) every 15 seconds; the upstream system may optionally push ProvideChargingRequests.req
  messages carrying per-vehicle charging schedules. The session opens with a WebSocket TLS handshake authenticated
  with HTTP Basic credentials issued by The Mobility House, followed by a BootNotification.req/.conf exchange.
humanURL: https://vdv-docs.tmh.energy/
baseURL: ''
x-baseurl-note: Deliberately empty, not a gap in the pass. The VDV 463 WebSocket-Secure endpoint is provisioned
  per customer site by The Mobility House at the time the site is enabled, and is delivered privately
  with the credentials; no base URL is stated anywhere in the public technical guideline. api.tmh.energy
  resolves and is a Mobility House host, but it answers HTTP 503 from nginx on every path probed (/, /openapi.json,
  /docs, /v1/openapi.json, /swagger.json, /api-docs, /redoc, 2026-08-30) and is named in no document,
  so it is not asserted as the base.
tags:
- VDV 463
- WebSocket
- Depot Management
- Charging Schedules
- Smart Charging
properties:
- type: Documentation
  url: https://vdv-docs.tmh.energy/
- type: GettingStarted
  url: https://vdv-docs.tmh.energy/initial-connection/initial-connection/
- type: Authentication
  url: authentication/the-mobility-house-authentication.yml
- type: ErrorCatalog
  url: errors/the-mobility-house-problem-types.yml
- type: DataModel
  url: data-model/the-mobility-house-data-model.yml
- type: Conformance
  url: conformance/the-mobility-house-conformance.yml