Introducing Charge Record V2
4 months ago
š¹ 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].