Skip to main content

reev API | Access & Use

This article explains how to get access to the reev API and what typical use cases exist.

Written by Llewellyn Nakielski
Updated yesterday

An API (Application Programming Interface) is a connection that allows different systems to communicate with each other. With the reev API, you can connect your charging infrastructure to other digital tools - for example for your internal billing system. Automate processes that were previously manual.


Requirements

  • You need a Business or Enterprise licence for the reev Platform.

  • If you currently use a different licence, you can upgrade your subscription directly in the Platform.


Requesting Access

Follow these steps to get access to the reev API:


Typical Use Cases for the reev API

The reev API enables direct integration of the reev Platform into existing systems, applications, or processes. It provides access to data on charging points, charging sessions, users, and energy flows.

Examples of how companies use the reev API include:

  1. Integration into external systems and dashboards: Integrate real‑time charging data into monitoring or management tools - for example, for billing, energy, or fleet management.
    Example: A partner company used the API to create a public kiosk display showing the live status of charging points. → View example

  2. Automated data processing: Export charging sessions and energy consumption data for internal processing or integration into ERP and CRM systems.

Tip: The API is particularly useful for companies that want to develop their own services or visualisations based on the reev Platform.

Note: The reev API currently supports data retrieval only (read‑only).

Writing or feeding data back into the reev Platform is not yet possible.


Frequently Asked Questions

What data can I access through the API?

You can retrieve information about charging points, sessions, users, tariffs, and energy flows.

How is the API authenticated?

Authentication is handled via API keys, which you receive once access has been granted. Details can be found in the technical documentation.

Can I test the API access?

There is currently no public sandbox or test environment.

All API accesses are created in the production environment and granted individually.

Did this answer your question?