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

Welcome to the developer hub and documentation for spirii!