Integration Options at a Glance
Stekker is designed to fit into your existing infrastructure, not replace it. Whether you manage a handful of charge points or operate a large fleet across multiple sites, there are several ways to connect your systems with Stekker.
This article covers the main integration protocols and when to use each one.
OCPP: Connecting Charge Points
OCPP (Open Charge Point Protocol) is the industry standard for communication between charge points and management systems. Stekker supports both OCPP 1.6 and OCPP 2.0.1.
In practice, your charge points connect to Stekker through your CPO (Charge Point Operator) — companies like E-Flux, Evesto, or Maxem. The CPO handles the direct OCPP connection with the charger, and Stekker integrates with the CPO to manage sessions and send power setpoints.
You do not need to configure OCPP yourself. Stekker and your CPO handle the technical setup. Your role is to ensure your charge points are registered with a supported CPO.
OCPI: Network Interoperability
OCPI (Open Charge Point Interface) enables interoperability between different charging networks. It allows drivers from one network to use charge points on another — similar to how roaming works for mobile phones.
Through OCPI, Stekker can exchange session data, tariff information, and authorization details with partner networks. This is particularly useful for organizations whose drivers need to charge at third-party locations, or who want to open their charge points to external users.
S2 Protocol: Energy Flexibility
The S2 protocol (EN 50491-12-2) is a European standard for communicating energy flexibility between devices and energy management systems. It defines how a flexible device — like an EV charger — can describe its capabilities and respond to control signals.
Stekker uses S2 to standardize flexibility communication, both internally and with external parties such as grid operators and aggregators. If your building management system or energy platform speaks S2, it can integrate directly with Stekker’s flexibility layer.
For more on how flexibility works in practice, see Understanding Imbalance Markets and Flexibility.
REST API: Custom Integrations
For organizations that need tailored integrations, Stekker offers a REST API. This allows you to programmatically access charging data, manage sessions, and integrate Stekker into your own applications or dashboards.
Typical use cases include:
- Pulling session data into your own reporting or billing system
- Automating card management across your organization
- Building custom dashboards that combine charging data with other operational metrics
- Integrating with fleet management software
The API uses standard REST conventions with JSON payloads and token-based authentication.
Edge Devices: Local Communication
StekkerEdge is a small hardware device (based on the Teltonika RUT956 router) installed at your site. It communicates locally with charge points and energy meters using ModBus, and bridges that data to the Stekker cloud via MQTT.
The edge device serves two purposes:
- Real-time data — it reads sensor values and meter data locally, providing faster and more reliable measurements than cloud-only polling
- Local resilience — even when internet connectivity is intermittent, the edge device can maintain basic charge point control
Edge devices are installed and configured by your installer as part of the site setup process.
When to Use Which Integration
| Need | Protocol |
|---|---|
| Connect charge points | OCPP (via your CPO) |
| Enable roaming between networks | OCPI |
| Energy flexibility with grid/BMS | S2 |
| Custom reporting or automation | REST API |
| Local metering and control | ModBus via StekkerEdge |
Building Management Systems
Stekker can also integrate with building management systems (BMS). If your building already has an energy management platform, Stekker can exchange data to coordinate EV charging with other building loads like HVAC, lighting, or battery storage. Contact our team to discuss your specific setup.
How to Request API Access
API access is available for Stekker customers. Contact your account manager or reach out to our support team to request API credentials and documentation. We will work with you to determine the right integration approach for your use case.
