We've introduced comprehensive charge box management capabilities, enabling you to programmatically manage your physical charging hardware through the API.
We're introducing comprehensive remote charger control and enhanced EVSE management to the Spirii API, enabling you to manage your charging infrastructure without physical site visits.
Additionally, we're introducing token and token group management, enabling you to manage your charging tokens programmatically.
Remote charge box commands
Soft Reset: Graceful restart preserving data and configurations
Hard Reset: Full hardware reboot for unresponsive charge boxes
EVSE management and commands
Transaction control
Remote Start: Initiate charging sessions remotely - essential for app-based authorization and driver support
Remote Stop: End active sessions remotely to resolve stuck transactions
Unlock Connector: Remotely release connector locks to assist drivers with stuck cables on AC chargers with sockets.
Retrieve EVSE Information: List all EVSEs or fetch specific EVSE details including status, connectors, and power capabilities
Update EVSE Settings: Modify properties like maximum power output and connector type for individual EVSEs
Change Connector Availability: Update OCPP availability status for maintenance without affecting the entire charge box
Tokens management - Full CRUD operations
Tokens (also known as ID tags or charge keys) are unique identifiers that authenticate users to initiate a charging session.
Spirii differentiates between three types of tokens:
RFIDs
virtual tokens
and vehicle tokens.
Use the new token endpoints to manage tokens for your drivers and network.
We introduce full CRUD operations for token management, incl. (dis)abling tokens.
Token Groups management - Full CRUD operations
In Spirii, a token group is an access management mechanism where only tokens inside a group can authorize charging at specified locations.
Use these new token groups endpoints to manage location access for your drivers and network.
We introduce full CRUD operations for token group management, incl. (dis)associating locations and tokens to token groups.
📌 New endpoints:
Remote charge box management
POST /chargeboxes/:id/reset
POST /chargeboxes/:id/reboot
EVSE management
POST /evses/:uid/connectors/:id/remote-start-transaction
POST /evses/:uid/connectors/:id/remote-stop-transaction
POST /evses/:uid/connectors/:id/unlock
GET /evses & GET /evses/:id
PATCH /evses/:id/connectors/:id
POST /evses/:id/connectors/:id/change-availability
With version 2.2.0, we have just released 2 major upgrades to the Spirii API:
Temporary EVSE Status
Spirii's Temporary EVSE status functionality allows the charge point operator (CPO) to modify the charger status shared with the e-Mobility Service Providers (eMSPs). This feature updates the displayed charger status in the eMSP apps without touching the actual charger status.
The CPO can utilize this functionality for multiple use cases:
Maintenance mode: Avoid having drivers turn up at the charger only to be disappointed, whilst keeping the charger available for the technician to work on it.
Commissioning: Create hype for new chargers being planned, installed, tested, and configured.
Parking sensors: Allow an external sensor system to update the status when the parking space in front of the charger becomes occupied.
Reservation system: Allow an external booking system to update the reservation status of the charger.
In addition to the existing GET endpoints, Locations V2 now includes the full CRUD operations, including the ability to create, update, and delete locations programmatically.
All partners using V1 should transition to V2 as soon as possible.
The V1 endpoint will remain operational for now, but will be fully sunset at a later date (to be announced).
If you use V1, please update your integrations accordingly and reach out if you need support.
📌 Breaking Changes Notice:
Some properties are not available in the V2 anymore and the structure has changes in a breaking manner, but if you are using V1, we strongly recommend migrating now to take advantage of the new capabilities and ensure long-term compatibility. See the API documentation for the full details.
We've introduced Locations V2 and Tariffs V2 under the Spirii API.
The Charge Point Operator (CPO) of public chargers can use these GET endpoints to comply with the EU's Alternative Fuel Infrastructure Regulation (AFIR) article 20, which went into effect on April 14th, 2025.
Additionally, the added endpoints provide extended data fields related to location management and the pricing of public charging compared to the legacy Locations endpoint.
Both endpoints are structured and formatted in compliance with OCPI version 2.3.0.
Added data for tariff type, price components, and price restrictions
📢 Migration & Next Steps
All partners using V1 should transition to V2 as soon as possible.
The V1 endpoint will remain operational for now, but will be fully sunset at a later date (to be announced).
If you use V1, please update your integrations accordingly and reach out if you need support.
📌 Breaking Changes Notice:
Some properties are not available in the V2 anymore and the structure has changes in a breaking manner, but if you are using V1, we strongly recommend migrating now to take advantage of the new capabilities and ensure long-term compatibility. See the API documentation for the full details.
We've introduced Transaction V2 under the Spirii API.
This new version increases readability, introduces new transaction properties and improves the overall response structure and filtering capabilities.
🔔 Action Required:
Partners using this endpoint should migrate to V2 as soon as possible.
🔄 Key Changes & Improvements
Change
Transaction V1
Transaction V2
Data Structure
N/A
Response structure changes:
auth object has been added.
location object now returns type, countryCode, isEligibleForRefund properties
price object has been expanded to include VAT and tariff information
-user object has been replaced by appUserId
chargingDetails has been added containing detailed charing information like charging status, state of charge meter start and stop values, and C02 emissions data
-company object has been added
paymentStatus object has been added
Data Structure
meterValues object contains all meter values
meterValues has been deprecated and replaced by meterStart and meterStop properties inside the chargingDetails object
Pagination
Offset-based
Cursor-based for better scalability
Filtering
Limited filtering options
Enhanced filtering based on multiple fields: ongoing ,chargeBoxId ,evseId,locationType ,transactionType ,voucherId
📢 Migration & Next Steps
All partners using V1 should transition to V2 as soon as possible.
The V1 endpoint will remain operational for now, but will be fully sunset at a later date (to be announced).
If you use V1, please update your integrations accordingly and reach out if you need support.
📌 Breaking Changes Notice:
Some properties are not available in the V2 anymore and the structure has changes in a breaking manner, but if you are using V1, we strongly recommend migrating now to take advantage of the new capabilities and ensure long-term compatibility. See the API documentation for the full details.
We've introduced Charge Detail Records V2 under the Spirii API.
This new version enhances performance, consistency, and scalability while improving response structure and filtering capabilities.
Expanded status values for better charge session tracking
Meter Values
Basic meter readings
More detailed energy consumption metrics
Timestamps
Unix timestamps
ISO 8601 format for consistency
📢 Migration & Next Steps
All partners using V1 should transition to V2 as soon as possible.
The V1 endpoint will remain operational for now, but will be fully sunset at a later date (to be announced).
If you use V1, please update your integrations accordingly and reach out if you need support.
📌 Breaking Changes Notice:
No immediate disruptions, but if you are using V1, we strongly recommend migrating now to take advantage of the new capabilities and ensure long-term compatibility.
For any questions or migration support, please reach out to support at [email protected].
