# Charging Sessions

Endpoints related to records of charging. See [Understanding charging data](/docs/understanding/charging_sessions) for how charging sessions (plug-in episodes), charging sub-sessions (per-mode segments) and energy usage intervals (actual energy delivery) relate to each other.

 - [DispatcherLog](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/dispatcherlog.md): Schema: #/components/schemas/DispatcherLog
 - [GET /charging_sessions](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sessions.md): List all charging sessions visible to the authenticated client. Each session represents one physical plug-in episode: its start/end are the plug-in and unplug times. A session contains one or more cha
 - [GET /charging_sessions/{charging_session_id}](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sessions-charging_session_id.md): Retrieve a specific charging session representing one physical plug-in episode: its start/end are the plug-in and unplug times. See [Understanding charging data](/docs/understanding/charging_sessions)
 - [POST /charging_sessions/{charging_session_id}/boost_start](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/post-charging_sessions-charging_session_id-boost_start.md): Start boost charging on this charging session's vehicle. Finishes the in-progress smart charging sub-session and starts a replacement boost sub-session, charging the vehicle continuously rather than a
 - [POST /charging_sessions/{charging_session_id}/boost_end](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/post-charging_sessions-charging_session_id-boost_end.md): End boost charging on this charging session's vehicle. Finishes the in-progress boost sub-session and starts a replacement smart charging sub-session, returning the vehicle to charging around the chea
 - [GET /charging_sub_sessions](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions.md): List all charging sub sessions visible to the authenticated client. A charging sub-session is a segment of a plug-in episode during which a single charging mode (SMART, BOOST, etc.) was active. Its st
 - [GET /charging_sub_sessions/{charging_sub_session_id}](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id.md): Retrieve a specific charging sub-session, representing a period of a plug-in episode during which a single charging mode was active. Its start/end mark when the mode started and stopped being active —
 - [GET /charging_sub_sessions/{charging_sub_session_id}/energy_usage](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-energy_usage.md): Retrieve periodic energy usage intervals for a specific charging sub-session. This is the endpoint to use to find out when energy was actually delivered to the vehicle. A sub-session's start/end only
 - [GET /charging_sub_sessions/{charging_sub_session_id}/flags](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-flags.md): Retrieve flags associated with a specific charging sub-session. Flags highlight particular types of issues or anomalies detected during a charging session, along with their root causes.
 - [GET /charging_sub_sessions/{charging_sub_session_id}/debug_metadata](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-debug_metadata.md): Retrieve debug metadata for a specific charging sub-session. Debug metadata exposes session-level diagnostic information such as start/finish reasons, the energy usage calculation and interpolation m
 - [GET /charging_sub_sessions/{charging_sub_session_id}/schedules](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-schedules.md): Retrieve schedules for a specific charging sub-session. Schedules represent charging instructions for a charging session. Each schedule specifies a current (in milliamps) and a time period during whi
 - [GET /charging_sub_sessions/{charging_sub_session_id}/schedule_plans](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-schedule_plans.md): Retrieve schedule plans for a specific charging sub-session. Schedule plans represent the charging plan parameters used to generate schedules for a charging session. Each plan contains information ab
 - [GET /charging_sub_sessions/{charging_sub_session_id}/assessment](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-charging_sub_sessions-charging_sub_session_id-assessment.md): Retrieve the performance assessment for a specific charging sub-session. The assessment contains performance metrics for completed charging sessions, including energy delivery ratios, charge rates, a
 - [POST /charging_sub_sessions/{charging_sub_session_id}/recalculate_energy_usages](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/post-charging_sub_sessions-charging_sub_session_id-recalculate_energy_usages.md): Triggers a recalculation of energy usages (and performance assessment) for a completed charging sub-session. Use `dry_run` to preview the recalculation without persisting changes, and `cap_overages` t
 - [GET /dispatcher_logs](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/get-dispatcher_logs.md): List all dispatcher logs for a charging session. These logs record Dispatch Command attempts to EVSEs or Vehicles.
 - [POST charging_sub_session.created](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/paths/charging_sub_session.created/post.md): A charging sub-session is created, representing a period of charging in a single mode.
 - [POST charging_sub_session.ended](https://developers.ev.energy/ev.energy-api-v2/charging-sessions/paths/charging_sub_session.ended/post.md): A charging sub-session has ended, representing a period of charging in a single mode.