Transactions and CDRs

Charging session data is at the heart of your eMobility business. It powers reporting, operations, customer support, billing, and sustainability tracking—whether you're managing a public charging network (CPO) or offering services to drivers (eMSP).

In Spirii’s platform, charging data is structured around two core entities:

Transactions: Transactions represent ongoing and recently completed sessions. They are continuously updated as new meter values are received from the charger.
Note: In Spirii's API, “transaction” refers to the flow of energy, not a financial payment.
Charge Detail Records (CDRs):CDRs represent finalized sessions, used for financial reconciliation, reporting, and auditing. Once a transaction is complete, a CDR is generated containing all relevant data—including pricing, energy consumed, and metadata.

Both of these entities provide valuable data that can be used for multiple use cases, including:

Setting up reporting and custom dashboards
Integrating fleet management and telematics solutions
Sustainability reporting

Retrieving Transactions and CDRs

You can retrieve both single records or lists of sessions from the Spirii API.

Retrieve a single record

Use this for support or investigation purposes.

Pass the transaction_id as a query parameter to fetch full session data.

Retrieve lists of records

Use this to power dashboards, reports, or integrations.

Supported filters include:

Mode (Filter by CPO (charging on your network) or EMP (charging by your drivers))
UpdatedAtFrom / UpdatedAtTo (Limit results to a specific time window (e.g., last month)).
Filter (Filter by specific fields like operator, user, location, or company)

Use limit and NextPageCursor to manage large payloads.

When to use each

Use Case	Use Transactions	Use CDRs
Real-time monitoring	✅	❌
Support cases (active session)	✅	❌
Support cases (completed sessions)	❌	✅
Final billing or cost calculation	❌	✅
Monthly reporting and analytics	❌	✅
Fleet management integration	✅	✅

Best practices

For real-time dashboards or active session monitoring, poll GET /transactions with care—respect rate limits.
For financial or sustainability reporting, sync and store finalized CDRs locally to reduce load and enable analysis.
Always map transaction_id, evse_id, location_id, and auth uid across systems for traceability.

Next steps

By integrating both Transactions and CDRs into your systems, you unlock a full view of your charging operations—covering live usage, financial tracking, and environmental impact.

Whether you're building fleet dashboards, enabling customer support, or running ESG analytics, Spirii’s charging data gives you the accuracy and flexibility to scale confidently.

Explore the API Reference to get started, or reach out to us if you need help designing the best integration for your business.