Stekker is hardware-agnostic. We don’t communicate directly with your charge point, but through the software platform that manages your charging infrastructure: the Charge Point Operator (CPO). In addition, we have direct API integrations with specific hardware manufacturers. This article provides a complete overview of all supported platforms, protocols and connector types.
CPO integrations (cloud-based)
Stekker sends charging profiles to the CPO, which forwards them to your charge point. The following CPO platforms are supported:
- E-Flux by Road — Fully supported via OCPP 1.6 and OCPP 2.0.1. The most widely used CPO integration in the Stekker network. Stekker supports both the classic E-Flux protocol and the newer E-Flux CSME platform.
- Evesto — Supported via OCPP 1.6. Commonly used for semi-public and private charging infrastructure in the Benelux region.
- Maxem — Custom API integration for charge points managed through the Maxem platform.
- Stekker CPP — Stekker’s own Charge Point Protocol. For parties that want to connect their charge points directly to Stekker without an intermediary CPO. Suitable for hardware partners and OEM integrations.
Direct hardware integrations
In addition to CPO integrations, Stekker has direct API connections with two hardware manufacturers. With these integrations, Stekker communicates directly with the manufacturer’s cloud API, without a CPO in between.
- Easee — Norwegian manufacturer of compact charge points for residential and commercial use. Stekker connects via the Easee Cloud API with support for start/stop control, configuration readout and automatic location detection. Users sign in with their Easee account to establish the connection.
- Zaptec — Stekker connects directly via the Zaptec Portal API. This is the recommended integration method for full smart charging support. Stekker reads the installation structure automatically and controls charging current through the Zaptec API. Zaptec Sense load balancing remains active alongside Stekker’s optimization.
Note: Zaptec charge points connected through a CPO (e.g. E-Flux) operate in Zaptec’s Cloud OCPP mode, which does not support smart charging profiles. If your Zaptec is currently managed by a CPO, switch to the direct Stekker integration for smart charging.
OCPP support
Most charge points communicate via OCPP (Open Charge Point Protocol), the industry standard for communication between charge points and management systems. Stekker supports:
- OCPP 1.6 — The most widely deployed version, supported by virtually all commercial charge points on the market.
- OCPP 2.0.1 — The newer version with improved security, device management and transaction handling.
The most important technical requirement is support for Smart Charging Profiles (the OCPP SetChargingProfile message). Without this capability, Stekker can monitor your sessions but cannot actively control them.
Connector types and power
Stekker works with all common connector types:
- AC (alternating current) — Both single-phase and three-phase, from 3.7 kW to 22 kW. This is the most common type at offices, parking garages and residential charge points. AC charging gives Stekker the most flexibility: vehicles are connected long enough to optimize the charging schedule.
- DC (direct current) — Higher power levels for fast charging. Stekker can control DC charge points, although the optimization window is more limited due to shorter session durations.
S2 protocol
Stekker supports the S2 protocol (EN 50491-12-2), an open standard for energy flexibility. Through S2, Stekker can communicate with any device that implements this standard — not just charge points but also battery energy storage systems (BESS) and other flexible assets.
S2 connections are set up per connector and enable bidirectional communication: the device reports its flexibility, and Stekker sends instructions back based on the optimization engine.
What if my charge point is not listed?
Stekker primarily communicates through CPO platforms, not directly with hardware. This means:
- If your charge point is connected to a CPO that supports OCPP 1.6 or 2.0.1, integration is often possible — even if that CPO is not yet listed above.
- If you are a hardware manufacturer and want to set up a direct integration, we offer Stekker CPP as our own protocol.
- Every location is unique. Get in touch for an assessment of your specific situation.
