🔹What’s new

A CPO can use our public facing APIs to build their own experience for managing home charging expenses and reimbursement. The core functionalities of the Spirii Platform abstract away the heavy lifting for them, letting them focus on the user experience and higher level functionalities. That means, the Spirii Platform still does:

• Charger configuration and authentication of Charging Sessions
• Management of Tokens, Locations, Reimbursement Rates
• Reimbursement validation
• Expense Report aggregation for Employees and Fleets
• Approval of expense reports
• Integration to PPS for end to end reimbursement (when the Fleet Customer uses PPS services)
• Generation of Driver and Fleet Expense report documents

📌 New endpoints:

GET /reimbursement/v1/expense-reports
GET /reimbursement/v1/expense-reports/{id}
GET /reimbursement/v1/expense-reports/{id}/document
POST /reimbursement/v1/expense-reports/{id}/approve

GET /reimbursement/v1/expenses/{id}
GET /reimbursement/v1/expenses/{id}/document
GET /reimbursement/v1/expenses/{id}/charge-detail-records/unlinked
POST /reimbursement/v1/expenses/{id}/charge-detail-records/add
POST /reimbursement/v1/expenses/{id}/charge-detail-records/remove

📖 Next steps

Explore the API Reference for detailed specifications

🔹 What's new?

We're introducing AFIR-compliant DATEX II v3 endpoints, enabling public access to energy infrastructure data for your charging network. These endpoints support the Alternative Fuels Infrastructure Regulation (AFIR) reporting requirements by exposing standardized static and dynamic charging infrastructure data.

Both endpoints are publicly accessible — no authentication required.

📌 New endpoints:

AFIR energy infrastructure

• GET /v2/afir/energy-infrastructure-tables
• GET /v2/afir/energy-infrastructure-statuses

🔄 Key changes & improvements

Both endpoints support:

• Gzip compression for optimized payload delivery
• Conditional caching via If-Modified-Since / 304 Not Modified
• Customer filtering via optional customerIds query parameter

📖 Next steps

Explore the API Reference [link] for detailed specifications

Read more in our guide here [link]

🔹 What's New?

We’ve enhanced the EVSE configuration capabilities with new power parameters for more precise control over EVSE electrical specifications.

🔄 Key changes & improvements

Updated endpoint:

• PATCH /evses/:id - Now supports additional power configuration fields

New fields:

• maxVoltage - Maximum voltage output (V) according to OCPI specification
• maxAmperage - Maximum current output (A) according to OCPI specification

Existing fields:

• maxElectricPower - Maximum power output (kW)
• standard - Connector type according to OCPI specification

These enhancements allow you to configure precise electrical parameters for each EVSE independently, enabling better alignment with physical hardware specifications without affecting other EVSEs on the same charge box.

📖 Next steps

For detailed field specifications and examples, visit our API Reference. If you have questions about implementing these new parameters, contact our support team.

🔹 What's new?

We've introduced comprehensive charge box management capabilities, enabling you to programmatically manage your physical charging hardware through the API.

📌 New endpoints:

Charge box management

• GET /chargeboxes
• GET /chargeboxes/:id
• GET /chargeboxes/models
• POST /chargeboxes
• DELETE /chargeboxes/:id

🔄 Key changes & improvements

📖 Next steps

• Explore the API Reference [link] for detailed specifications
• Read more in our guide here [link]

🔹 What's new?

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

Token management

• GET /tokens/:id
• GET /tokens
• POST /tokens
• POST /tokens/:id/enable
• POST /tokens/:id/disable
• PATCH /tokens/:id
• DELETE /tokens/:id

Token group management

• GET /token-groups/:id
• GET /token-groups
• POST /token-groups
• POST /token-groups/:id/enable
• POST /token-groups/:id/disable
• PATCH /token-groups/:id
• DELETE /token-groups/:id
• GET /token-groups/:id/locations
• POST /token-groups/:id/locations/:locationId
• DELETE /token-groups/:id/locations/:locationId
• GET /token-groups/:id/tokens
• POST /token-groups/:id/tokens/:tokenId
• DELETE /token-groups/:id/tokens/:tokenId

🔄 Key changes & improvements

📢 Use cases examples

For NOC & support teams:

• Troubleshoot issues remotely without site visits
• Assist drivers with authorization and stuck sessions
• Unlock connectors when cables are stuck

For CPOs:

• Build custom monitoring and alerting solutions
• Perform maintenance without taking charge boxes offline
• Manage fleet operations efficiently
• Bulk-create and manage tokens
• Manage location access via token groups

📖 Next steps

• Explore the API Reference [link] for detailed specifications
• Read more in our guide here [link]

🔹 What's New?

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.

📌 New Endpoints:
POSt /v2/temporary-evse-statuses
GET /v2/temporary-evse-statuses
GET /v2/temporary-evse-statuses/{id}
PATCH /v2/temporary-evse-statuses/{id}
DELETE /v2/temporary-evse-statuses/{id}

Locations V2 - Full CRUD operations

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.

📌 New Endpoints:
POST /v2/locations
PATCH /v2/locations/{id}
DELETE /v2/locations/{id}

❌ What's Deprecated?

The old Locations V1 update endpoint is now deprecated under the Spirii Legacy API.

📌 Deprecated Endpoints:
PUT /locations

🔔 Action Required:
Partners using this endpoint should migrate to V2 as soon as possible.

🔄 Key Changes & Improvements

📢 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.

🔹 What's New?

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.

📌 New Endpoints:
GET /v2/locations
GET /v2/locations/{id}
GET /v2/tariffs/{id}

❌ What's Deprecated?

The old Locations V1 endpoint is now deprecated under the Spirii Legacy API.

📌 Deprecated Endpoints:
GET /locations
GET /locations/{id}

🔔 Action Required:
Partners using this endpoint should migrate to V2 as soon as possible.

🔄 Key Changes & Improvements

📢 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 fixed various bugs across the Transaction V2 and Voucher endpoints.

🔄 Key Changes & Improvements

🔹 What's New?

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.

📌 New Endpoint:
GET /v2/transactions

📌 New Endpoint:
GET /v2/transactions/{id}

❌ What's Deprecated?

The old Transaction V1 endpoint is now deprecated under the Spirii Legacy API.

📌 Deprecated Endpoint:
GET /v1/transactions

GET /v1/transactions/{id}

🔔 Action Required:
Partners using this endpoint should migrate to V2 as soon as possible.

🔄 Key Changes & Improvements

📢 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.

🔹 What's New?

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.

📌 New Endpoint:
GET /v2/charge-records

❌ What's Deprecated?

The old Charge Record V1 endpoint is now deprecated under the Spirii Legacy API.

📌 Deprecated Endpoint:
GET /v1/charge-records

🔔 Action Required:
Partners using this endpoint should migrate to V2 as soon as possible.

🔄 Key Changes & Improvements

📢 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].