Skip to main content

Integration Options

Pleevi supports multiple ways to integrate with your charging infrastructure. Depending on your setup, you can choose one or combine several of these methods.

Overview

Integration MethodCapabilitiesData FlowSchedule DeliveryBest For
MQTTIngress, EgressYou publish measurements & transactions to our MQTT brokerSubscribe to MQTT topicsLocal controllers, EMS platforms, real-time bidirectional communication
APIConfiguration, Driver I/OManage sites, topologies, and optimization settings via REST APIDriver-facing endpoints for session input and schedulesSite setup and management, driver-facing applications
Smart OCPP BrokerIngress, Egress, Driver IdentificationAutomatic, we read OCPP messages from your charging stationsSent directly to the charging station via OCPPMinimal integration effort, no code changes needed
Eniris Smart Grid OneIngress, EgressAutomatic, Eniris reports device metrics to PleeviSent directly to the Eniris controllerSites with Eniris hardware, fully managed integration
MINTIngressAutomatic, MINT reports energy measurements to Pleevi/Sites with MINT smart energy meters
OCPIIngress, EgressVia OCPI protocol from your CPMSSmart Charging commands via OCPICPMSs with OCPI support
WithTheGridComing soonComing soonComing soonSites using WithTheGrid teleport controller
CustomDepends on your setupDepends on your setupDepends on your setupHave a different system? Contact us, we're always open to discuss new integrations
Capability definitions
  • Ingress: Sending measurement data and transactions to Pleevi.
  • Egress: Receiving optimized charging schedules from Pleevi.
  • Configuration: Creating and managing sites, topologies, and optimization settings.
  • Driver I/O: Driver-facing endpoints for session input (departure time, energy needs) and retrieving personal schedules.
  • Driver Identification: Identifying drivers via badge ID (RFID token) from charging sessions.

The API does not support data ingress or egress — use MQTT, the Smart OCPP Broker, or Eniris for sending measurements/transactions and receiving schedules. Use the API or Portal to manage site configuration.

Combining Integration Methods

These methods are not mutually exclusive. Common combinations include:

  • OCPP Broker + API: Use the OCPP broker to automatically capture measurements and transactions from your charging stations, while using the API for site configuration and management.
  • OCPP Broker + MQTT: Use the OCPP broker for charging station data, while using MQTT to send additional site data (solar, building load) and receive optimized schedules.
  • OCPP Broker for driver identification only: Use the OCPP broker solely to identify drivers via their badge ID (from OCPP StartTransaction events), while handling data ingress and schedule delivery through MQTT. See Driver Identification Mode for details.
  • API + MQTT: Use MQTT for real-time data ingress and schedule egress, while using the API for site configuration, activation, and management.
  • Eniris + OCPP Broker: Use the Eniris controller for local energy management and charging, while using the OCPP broker for driver identification.

Getting Started

Choose the integration method that fits your infrastructure:

  • MQTT Integration, Connect to our MQTT broker to send data and receive schedules in real time.
  • API Integration, Configure sites, manage topologies, and access driver-facing endpoints.
  • Smart OCPP Broker, Point your charging stations at our WebSocket endpoint and we handle the rest.
  • Eniris Smart Grid One, If you have Eniris hardware on-site, we integrate directly with it.
  • MINT, Integrate MINT smart energy meters for site-level measurements.
  • OCPI, Connect your CPMS via the OCPI protocol.
  • WithTheGrid, Teleport integration (coming soon).
tip

Not sure which integration method to use? If you have an Eniris Smart Grid One or can use the Smart OCPP Broker, those require the least integration effort. If you need more control or want to send additional site data, combine them with the API or MQTT integration.