Skip to content

VDV 261 overview

Version status

BetterFleet has checked this material against its licensed copy of VDV Recommendation 261, Edition 2, issue 05/2023. VDV lists issue 07/2024 as the current publication. That issue has not yet been compared, so BetterFleet does not claim conformance with the current issue.

VDV 261 defines the Vehicle to Infrastructure Communication Protocol (V2ICP), used to exchange operational charging and preconditioning data between the EVCC in a vehicle and a backend through ISO 15118 VAS 3 InternetAccess.

Repository scope

This repository provides a FastAPI facade for the 05/2023 V2ICP JSON contract, VIN/EVCC-bound Basic authentication, Manage Core directive resolution, generated schemas, and supporting documentation. It does not establish VAS sessions, enforce the surrounding IPv6 or TLS profile, or persist diagnostics.

BetterFleet surfaces

Artifact Classification Current behaviour
POST /vdv261/v2icp/messages VDV-aligned wire surface Authenticates and validates a flat vehicle request, resolves the current Manage Core directive, and returns a full seq = 0 response or the applicable later delta.
POST /vdv261/v2icp/diagnostics BetterFleet extension Accepts and acknowledges a diagnostic event; it is not persisted.
GET /vdv261/schemas BetterFleet extension Lists published schema identifiers.
GET /vdv261/schemas/{schema_name} BetterFleet extension Returns a model's JSON schema.
GET /vdv261/openapi.json BetterFleet extension Provides the generated API definition.

Standard context

  • V2ICP uses a flat JSON request and response; there is no parameters wrapper.
  • The EVCC initiates HTTPS over IPv6 through VAS 3 on port 443.
  • BetterFleet requires the VIN as the Basic Authentication username and a configured per-vehicle password bound to the request EVCC ID.
  • seq = 0 is the full-state exchange; later exchanges normally carry deltas.
  • h2_stat and bat_stat are required in every vehicle request under explicit requirement V2ICP-71.
  • The facade implements the HTTP application boundary and preconditioning directive path. VAS transport, session lifecycle, deployment configuration, and physical-vehicle conformance remain separate integration concerns.

Read this section in order