Charging point health

Check the health of a charging point via the Asset endpoints of the Core API. When a driver reports that a charging point does not work, call center agents and AI support assistants get everything they need for a first diagnosis in a single call: the current status and its recent history, the controller and its last OCPP activity, known issues, recent OCPP messages and authorization attempts, the last reboot, and the service partners of the location.

Health check flow

Authenticate once with an API key to obtain a Bearer token, then request the health snapshot with the charging point’s uuid. The endpoint is available to API keys only; the API key’s role needs the permission asset:chargepoints:health. A charging point that does not belong to your tenant returns 404. For authentication details, see the Authentication page.

1 · Authenticate

POST /api/v1/oauth/token
Content-Type: application/json

{ "username": "<public key>", "password": "<private key>", "tenant": "..." }

2 · Get the health snapshot

GET /api/v1/assets/chargepoints/{uuid}/health
Authorization: Bearer <access_token>

200 OK

{
  "chargepoint_health": {
    "chargepoint": {
      "uuid": "7f3e2b1a-9c4d-4e8f-a2b6-3d5c7e9f1a2b",
      "evse_id": "DE*CHC*E123456*1",
      "status": "Faulted"
    },
    "controller": {
      "manufacturer": "Musterwerk",
      "firmware": "2.4.1",
      "last_ocpp_activity": "2026-10-07 09:41:58"
    },
    "statuses": [
      { "status": "Faulted", "error_code": "GroundFailure", "created_at": "2026-10-07 09:12:03" }
    ],
    "issues": [{ "status": "new", "subject": "Ground failure at connector 1" }],
    "service_partners": [{ "partner_name": "Muster Elektro GmbH", "partner_type": "Service" }]
  }
}

The response is shortened. The full snapshot also contains the location, OCPP messages, authorization requests, the last reboot and the parking sensor, see Returns a health snapshot of a charge point. Timestamps are server-local time in Y-m-d H:i:s, without a time zone.

Additional use cases

Start from the EVSE ID: If the driver only reads the EVSE ID from the charging point, find its uuid first via Retrieves chargepoints with the evse_id query parameter. The * separators are optional.
AI support assistant: Offer the health snapshot as a tool to an AI assistant, using a dedicated API key whose role grants only the read permissions it needs. The assistant answers the driver’s first questions and hands over to a person when on-site work is needed.
Fix the problem remotely: When the snapshot points to a stuck cable or an unresponsive controller, send an unlock or soft_reset command via the Control endpoints of the Core API.
Commissioning on site: A technician checks a newly installed charging point: is the controller online, which firmware does it run, did it boot correctly.

Getting started

Best Practices

Health check flow

Additional use cases

​Health check flow

​Additional use cases

​Related topics

Health check flow

Additional use cases

Related topics