🔹 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

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.