Fleet management integration

Reducing costs and making your fleet operation as efficient as possible is essential for success in the world of mobility.

At Spirii, we focus our expertise on our charging and mobility platform and how to utilize it to enhance the efficiency of your fleet business. We are, however, aware that more dimensions are needed to succeed.

A critical component is often a fleet management or telematics provider, which can accurately track your vehicles in real-time, monitor their status, and plan the most efficient routes for them.

This guide explains how to integrate your preferred fleet management solution with Spirii's charging platform to:

Improve route planning with charger locations and availability
Automate reporting and operational workflows
Gain complete visibility into fleet performance and charging cost

Key integration data

Below are the core API resources used in a fleet management integration.

Locations

The GET Locations endpoint includes key metadata on the chargers at your depot or other sites where you operate the chargers.

Useful data fields include:

Address and coordinates (where the chargers are placed)
Publish (the public availability of the chargers)
EVSEs (array of EVSEs on the location)
- Status (the charging status of the EVSE, e.g., "charging" or "available")

Use this data to assess capacity at depot sites or plan routing based on the charger availability.

Transactions

The GET Transactions endpoint will list all the ongoing and completed charging sessions for a given location, token, or simply across the full network.

Useful data fields include:

EVSE ID (the unique ID of the EVSE of the charger)
Auth data (range of data on who charged, e.g., a specific app user or charge token)
Consumed (the amount of kWhs consumed so far during the session)
vehichleStateOfCharge (the latest battery percentage reading from the vehicle - only available on DC chargers)
Location data (range of contextual data on the location of the charger)
Roaming data (range of data if the session included roaming)

Use this to track charging sessions for your fleet vehicles live.

Charge Detail Records (CDRs)

The GET CDRs endpoint contains the data of a completed charging session. In Spirii, we populate the CDR with various contextual data to facilitate easy reporting and automation.

Useful data fields include:

Transaction ID (The unique ID of the CDR)
EVSE ID (the unique ID of the EVSE of the charger)
Auth data (range of data on who charged, e.g., an app user or token)
Consumed (the amount of kWhs consumed during the session)
Price data (range of data including the total charging price incl. and excl. VAT, currency, VAT rate, link to tariffs, etc.)
Location data (range of contextual data on the location of the charger)

Use this data to populate consumption reports, monitor cost efficiency, and trigger downstream workflows.

Additional integration data

Below are additional data resources that may be beneficial for your use case

App users

If you have partnered with Spirii for a white-label charging app, the GET App Users endpoint lists all the app users who have signed up.

Use this to pair and enrich the transaction and CDR data where these drivers have been charging.

Tariffs

The GET Tariffs endpoint will provide you with the details of the price and conditions for charging at one of your locations.

Use this to customize cost-optimized pricing strategies.

Sample fleet management integration flow

The fleet management system schedules regular polling (e.g., every 5 minutes) for GET Locations and GET Transactions to receive near-real-time updates on charger availability and ongoing sessions.
The fleet management system triggers a daily sync (e.g., at the end of the day) for GET CDRs to pull data on the full day's consumption.

Best practices

Map identifiers across platforms like EVSE IDs and Location IDs to your internal depot/fleet structure for easier reporting
Use incremental syncs with updated_at or pagination to avoid large payloads.
Store CDRs locally to reduce external API calls for frequent reporting
Handle retries and error states gracefully when polling endpoints
Use rate limiting and avoid polling more than once per minute per resource

Start integrating now and unlock smarter fleet charging with Spirii. For guidance or assistance, check out our support resources or contact us directly.