24 days ago

(v.2.0.1) Bug fixes

We fixed various bugs across the Transaction V2 and Voucher endpoints.

🔄 Key Changes & Improvements

Change	Endpoints	Description
Bug fix	GET https://api.spirii.com/v2/transactions GET https://api.spirii.com/v2/transactions/{id}	Fixed an issue with the `startedAt` filter not being applied
Bug fix	GET https://api.spirii.com/vouchers GET https://api.spirii.com/vouchers/{id}	Fixed an issue with retrieving voucher groups where the `companyId` was `null`
Bug fix	GET https://api.spirii.com/vouchers GET https://api.spirii.com/vouchers/{id}	Fixed an issue where the response included deleted voucher groups (`deletedAt` timestamp being populated). These are now filtered out.

2 months ago

Introducing Transaction V2

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

3 months ago

Introducing Charge Record V2

🔹 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

Change	Charge Record V1	Charge Record V2
Base Path	`/v1/charge-records`	`/v2/charge-records`
Data Structure	Flattened response format	Structured response with nested data
Filtering	Limited filtering options	Enhanced filtering on multiple fields (e.g., start/end timestamps, CPO ID, EMP ID)
Pagination	Offset-based	Cursor-based for better scalability
Status Field	Limited status values	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].

7 months ago

Welcome to spirii

Welcome to the developer hub and documentation for spirii!