Upcoming Changes to Closed Session APIs

Status: Planned

Effective FromFull Deprecation date
August 1, 2026January 1, 2027

Summary

We are introducing new public API endpoints for accessing closed charging sessions.

In the future, the existing public session endpoints will only provide access to open sessions. Existing endpoints used to access closed sessions will be removed.

The new API for closed sessions will require some query changes:

  • You must provide an installation ID, charging station ID, or user ID.
  • You must provide a time range.
  • The API will not return a total page count. Instead, pagination will be handled using a page cursor.

High-level plan

1. New public API endpoint

A new public API endpoint for archived sessions will be introduced.

This endpoint will become the new public endpoint for accessing archived closed sessions. Customers will be informed as soon as the API is available.

2. Deprecation of legacy session endpoints

Legacy session endpoints that expose closed sessions will be marked as deprecated once the new endpoint is available.

Deprecation warnings will also be returned from the affected endpoints.

3. Change in data availability effective August 1, 2026

On August 1, 2026, we will:

  • Stop exposing sessions older than 2 years through the existing public endpoints.
  • Keep the existing endpoints working as before for sessions younger than 2 years.
ℹ️

Third parties only need to change behavior at this stage if they require access to sessions older than 2 years.

4. Full migration to new API no later than January 1, 2027

On January 1, 2027 at the latest:

  • All closed sessions must be queried through the new archived sessions API.
  • Legacy endpoints for closed sessions will be removed.

Breaking change notice

The change effective August 1, 2026 introduces a breaking change for current API integrations:

  • Sessions older than 2 years will no longer be available through the existing public API.
  • Integrations that require access to closed sessions older than 2 years must adopt the new archived sessions API once it becomes available.

This timeline allows sufficient time to follow the full deprecation procedure, including removal of the legacy endpoints for closed sessions by January 1, 2027.

⚠️

Action Required:

If your integration relies on access to closed sessions older than 2 years, prepare to migrate to the new archived sessions API when it becomes available.

If your integration only requires:

  • open sessions, or
  • closed sessions younger than 2 years during the initial transition period,

You do not need to make immediate changes for the August 1, 2026 change.