Changelog

​

Manage reimbursement rates in Spirii Connect

​

What’s improved

• Rates tab on each location: every reimbursement rate for the location, with its start date, end date, currency, and rate per kWh. The active rate also shows on the location overview.
• Add and edit rates: set a start date, an optional end date, the currency, and the rate per kWh.
• Supporting documents: attach evidence such as an electricity bill when you add or edit a rate, then download or remove it later. Use it to validate a rate or to support a tax audit.
• Applied rate on the CDR: the CDR details show which reimbursement rate was applied to the session.
• Checked on save: a rate’s period is checked against the location’s other rates when you save it. If the period conflicts, the save is rejected and an error explains why.

​

Why it matters

​

How it works

​

What a rate supports

• Each rate is a flat price per kWh for a period. Variable contracts such as spot-price tariffs, day and night pricing, and regulated rates aren’t supported.
• A rate must be above 0 and no higher than 10 per kWh, with at most four decimals. The maximum is the same in every currency.
• Rates can’t be deleted in Connect. Delete a rate with the Spirii API, unless it’s locked because an expense report has used it.
• Drivers can’t add or manage rates in Spirii Go or a branded app.

​

Who is this for?

• Segment: B2B Fleet, and CPOs serving fleet customers
• Users: Fleet managers in Spirii Connect; operators onboarding fleet customers onto reimbursement; integrators managing rates through the Spirii API
• Markets: All markets

​

Next steps

​

Reimburse every session at a home charger

​

What’s improved

• New location setting: Reimburse all sessions to the location owner, in the Reimbursement section when you create or edit a location in Connect.
• Off by default: existing locations keep reimbursing charge key sessions only.
• Visible on the overview: the Pricing and billing card shows whether the location reimburses charge key sessions only or all sessions.
• Self-serve: you set it when you configure the location, with no request to Spirii.

​

Why it matters

​

Single-driver locations

​

Who is this for?

• Segment: B2B Fleet, and CPOs serving fleet customers
• Users: Operators and fleet managers who create and edit locations in Spirii Connect; company car drivers charging at home
• Markets: All markets

​

Next steps

​

Lower reservations on private, non-roaming locations

​

What’s improved

• The reservation is still calculated from the location’s tariff, using a lower multiplier for these locations
• Locations that are public, or that have roaming enabled, are unchanged
• The minimum reservation amount has been removed, so locations on low tariffs see the full reduction rather than being rounded back up

​

Why it matters

​

How it works

• Public availability is off
• Roaming is not enabled

​

Reservation amounts

​

Who is this for?

• Segment: B2B Fleet, and workplace or employee charging in particular
• Users: Drivers paying by card at private locations; CPOs and site owners managing non-public locations in Spirii Connect
• Markets: All markets

​

Next steps

​

Chargers moving to a new OCPP endpoint

​

What’s improved

​

Timeline

​

What happens when a charger moves

• Its OCPP URL changes to wss://ocpp.spirii.com and it restarts.
• It’s offline for the restart, usually under a minute. If a charger is still offline 30 minutes after its migration, we investigate.
• We never migrate a charger with an active or unfinished session, since the restart would cancel it.
• Nothing else changes: tariffs, location, and historical data stay exactly as they are.

​

What you need to do

​

Do you connect through a proxy?

• Does our charger connect to Spirii directly, or through your platform?
• If through your platform, can you repoint the OCPP connection to wss://ocpp.spirii.com, and confirm it supports TLS 1.2?

​

Hardware that can’t move yet

​

Who is this for?

• Segment: All segments operating charge points through Connect
• Users: CPOs and charge point owners using Spirii Connect
• Markets: All markets

​

Next steps

​

Introducing App User V2 endpoints

​

What’s new

​

New endpoints

• GET /v2/app-users — retrieves a paginated list of app users
• POST /v2/app-users — create a new app user
• GET /v2/app-users/{id} — get a single app user by id
• PUT /v2/app-users/{id} — update an existing app user

​

Vouchers and voucher groups

​

What’s new

​

New endpoints

• GET /v2/vouchers
• POST /v2/vouchers
• GET /v2/vouchers/{id}
• PATCH /v2/vouchers/{id}
• DELETE /v2/vouchers/{id}
• GET /v2/vouchers/{id}/tokens
• POST /v2/vouchers/{id}/tokens/{tokenId}
• DELETE /v2/vouchers/{id}/tokens/{tokenId}

• GET /v2/voucher-groups
• POST /v2/voucher-groups
• GET /v2/voucher-groups/{id}
• PATCH /v2/voucher-groups/{id}
• DELETE /v2/voucher-groups/{id}
• GET /v2/voucher-groups/{id}/vouchers
• GET /v2/voucher-groups/{id}/locations
• POST /v2/voucher-groups/{id}/locations/{locationId}
• DELETE /v2/voucher-groups/{id}/locations/{locationId}

​

Next steps

​

Price Optimised Charging

​

What’s new

• No more manually scheduling sessions around tariff hours
• The system monitors electricity prices and charges when it’s cheapest
• Vehicles are always ready on time — the schedule is built around your needs
• If something changes, you can override any session instantly in Connect

​

Why it matters

​

How it works

• Set a charging window (start time → end time) and specify how many hours of charge are needed. Spirii selects the cheapest intervals within that window automatically.
• Powered by live spot price data from Nordpool/ENTSO-E, with fallback to day-ahead forecasted prices when final prices are unavailable.
• The system prevents schedules from overlapping with opening hours, at both the frontend and backend level.

​

Hardware compatibility

​

Who is this for?

• Segment: B2B Fleet
• Users: Fleet managers and site managers operating via Spirii Connect
• Markets: Austria, Belgium, Germany, Denmark, Estonia, Spain, Finland, France, Great Britain, Lithuania, Latvia, Netherlands, Norway, Poland, Portugal, Sweden

​

Introducing home charging reimbursement rates

​

What’s new

​

New endpoints

• GET /reimbursement/rates/v1
• POST /reimbursement/rates/v1
• PATCH /reimbursement/rates/v1/{id}

​

Next steps

​

Expense reports for charging at home

​

What’s new

• As a Fleet Manager or Operator in Connect, you can now receive expense reports:
  • Via the public API
  • As a PDF, emailed to you or downloaded via Connect
  • As a CSV file downloaded via Connect

​

Why it matters

​

Who is this for?

​

Introducing smart payment reservations

​

What’s improved

• This guarantees a reserved amount high enough to cover the cost of the charging session, but not unnecessarily high.
• If the charging ends up more expensive, we attempt to increment the reservation (where possible) to the new amount.

• If you have to start over at the charge point, we don’t create a new reservation on your card — one is enough.

• We retry payment for the charging session a few times over the following days.

​

Why it matters

​

Soft delete for charge keys in Connect UI

​

What’s new

• Soft delete action in the charge keys sidebar
• Soft deleting a charge key also unlinks the payment method from the charge key
• Confirmation modal

​

Why it matters

​

Who is this for?

​

Introducing home charging reimbursements

​

What’s new

​

New endpoints

• GET /reimbursement/v1/expense-reports
• GET /reimbursement/v1/expense-reports/{id}
• GET /reimbursement/v1/expense-reports/{id}/document
• POST /reimbursement/v1/expense-reports/{id}/approve
• GET /reimbursement/v1/expenses/{id}
• GET /reimbursement/v1/expenses/{id}/document
• GET /reimbursement/v1/expenses/{id}/charge-detail-records/unlinked
• POST /reimbursement/v1/expenses/{id}/charge-detail-records/add
• POST /reimbursement/v1/expenses/{id}/charge-detail-records/remove

​

Next steps

​

AFIR DATEX II-ready API endpoints

​

What’s new

• Static data endpoints: full snapshots of sites, stations, and connectors
• Dynamic data endpoints: real-time availability and up-to-date pricing information
• Smart sync (delta pulls): support for If-Modified-Since headers, letting National Access Points pull only changed data, reducing bandwidth and improving sync speed

​

Why it matters

​

AFIR — DATEX II energy infrastructure data

​

What’s new

​

New endpoints

• GET /v2/afir/energy-infrastructure-tables
• GET /v2/afir/energy-infrastructure-statuses

​

Key changes and improvements

• Gzip compression for optimised payload delivery
• Conditional caching via If-Modified-Since / 304 Not Modified
• Customer filtering via the optional customerIds query parameter

​

Next steps

• Explore the API Reference for detailed specifications.
• Read more in the AFIR compliance guide.

​

Upgraded EVSE power settings and opening hours

​

What’s improved

• EVSE power settings: added configuration options for maximum output voltage and maximum output current (amps) to enable precise electrical parameter control per EVSE. Also available in the Spirii API.
• Opening hours UI: improved usability for opening hours configuration. Public availability settings have moved out of the opening hours modal and are now controlled from the location edit page.

​

Why it matters

• Flexible connector power settings allow for more accurate EVSE power data and boost roaming exposure of EVSEs.
• The opening hours UI now more clearly distinguishes between 24/7 availability and specific day-based schedules.

​

Reduced failed payments with advanced reservation amount logic

​

What’s improved

• Instead of a fixed pre-authorisation amount per country or operator, we now base the reservation amount on the tariff at each location.
• This produces a reservation amount much closer to the actual price for most users at the location.

​

Why it matters

​

Enhanced EVSE power settings

​

What’s new

​

Key changes and improvements

• PATCH /evses/{id} — now supports additional power configuration fields

• maxVoltage — maximum voltage output (V), per the OCPI specification
• maxAmperage — maximum current output (A), per the OCPI specification

• maxElectricPower — maximum power output (kW)
• standard — connector type, per the OCPI specification

​

Next steps

​

Dual user roles for more flexibility

​

What’s new

• Each user can now have multiple roles (for example, Fleet Manager and Supporter).
• The Fleet Manager role has been updated to handle reimbursements.

​

Why it matters

​

Introducing expense management for home reimbursements

​

What’s new

• Let the Spirii platform gather all the charging data and prepare the expense management files.
• Use the files in your own payroll system to pay employees.
• Optionally, add or remove CDRs to include in the expense report.

​

Why it matters

• This home reimbursement model lets fleet operators offer home charging to their employees.
• It’s a light setup with easy onboarding.

​

Who is this for?

​

Upgraded exports

​

What’s improved

• Dashboard export: added an EVSE ID column for better charge point identification.
• CDR exports: now include the billing customer CRM ID for easier customer identification.

​

Why it matters

​

Upgraded installer role

​

What’s improved

• Location lookup — find and access installation sites quickly
• Charge box and connector management — view, add, and configure hardware during installation
• Charge box actions — perform essential actions without needing full admin access
• Session access for testing — verify installations are working correctly in real time

​

Why it matters

• Previously, the installer only had access to order lookup, which restricted their ability to work efficiently.
• Business information stays secure: installers cannot view tariffs or pricing details.

​

Charge box management endpoints

​

What’s new

​

New endpoints

• GET /chargeboxes
• GET /chargeboxes/{id}
• GET /chargeboxes/models
• POST /chargeboxes
• DELETE /chargeboxes/{id}

​

Key changes and improvements

​

Next steps

​

Enhanced remote charger control, EVSE management, and charge key management

​

What’s new

​

Remote charge box commands

• Soft reset: graceful restart that preserves data and configurations
• Hard reset: full hardware reboot for unresponsive charge boxes

​

EVSE management and commands

• Transaction control
  • Remote start: initiate charging sessions remotely
  • Remote stop: end active sessions remotely
• Unlock connector: remotely release connector locks on AC chargers
• Retrieve EVSE information: list all EVSEs or fetch specific details
• Update EVSE settings: modify properties such as maximum power output
• Change connector availability: update OCPP availability status

​

Charge key management — full CRUD operations

​

Charge key group management — full CRUD operations

​

New endpoints

• POST /chargeboxes/{id}/reset
• POST /chargeboxes/{id}/reboot

• POST /evses/{uid}/connectors/{id}/remote-start-transaction
• POST /evses/{uid}/connectors/{id}/remote-stop-transaction
• POST /evses/{uid}/connectors/{id}/unlock
• GET /evses
• GET /evses/{id}
• PATCH /evses/{id}/connectors/{connectorId}
• POST /evses/{id}/connectors/{connectorId}/change-availability

• GET /tokens
• GET /tokens/{id}
• POST /tokens
• PATCH /tokens/{id}
• DELETE /tokens/{id}
• POST /tokens/{id}/enable
• POST /tokens/{id}/disable

• GET /token-groups
• GET /token-groups/{id}
• POST /token-groups
• PATCH /token-groups/{id}
• DELETE /token-groups/{id}
• POST /token-groups/{id}/enable
• POST /token-groups/{id}/disable
• GET /token-groups/{id}/locations
• POST /token-groups/{id}/locations/{locationId}
• DELETE /token-groups/{id}/locations/{locationId}
• GET /token-groups/{id}/tokens
• POST /token-groups/{id}/tokens/{tokenId}
• DELETE /token-groups/{id}/tokens/{tokenId}

​

Use cases

• Troubleshoot issues remotely without site visits
• Assist drivers with authorisation and stuck sessions
• Unlock connectors when cables are stuck

• Build custom monitoring and alerting solutions
• Perform maintenance without taking charge boxes offline
• Manage fleet operations efficiently
• Bulk-create and manage charge keys
• Manage location access via charge key groups

​

Next steps

• Read more about remote commands.
• Explore the API Reference for implementation details.

​

Introducing temporary EVSE status and full Locations CRUD

​

What’s new

​

Temporary EVSE status

• Maintenance mode
• Commissioning
• Parking sensors
• Reservation systems

• POST /v2/temporary-evse-statuses
• GET /v2/temporary-evse-statuses
• GET /v2/temporary-evse-statuses/{id}
• PATCH /v2/temporary-evse-statuses/{id}
• DELETE /v2/temporary-evse-statuses/{id}

​

Locations V2 — full CRUD operations

• POST /v2/locations
• PATCH /v2/locations/{id}
• DELETE /v2/locations/{id}

​

What’s deprecated

​

Migration and next steps

• All V1 partners should transition to V2 immediately.
• The V1 endpoint remains operational but will be fully sunset at a later date.
• Breaking changes exist; migrating to V2 is recommended.
• Read more about temporary EVSE status.

​

Introducing Locations V2 and Tariffs V2 for AFIR compliance

​

What’s new

• GET /v2/locations
• GET /v2/locations/{id}
• GET /v2/tariffs/{id}

​

What’s deprecated

• GET /locations
• GET /locations/{id}

​

Key changes and improvements

​

Migration and next steps

• All partners using V1 should transition to V2 as soon as possible.
• The V1 endpoint remains operational for now but will be fully sunset at a later date (to be announced).
• If you use V1, update your integrations accordingly and reach out if you need support.

​

Bug fixes

​

What’s fixed

​

Introducing Transaction V2

​

What’s new

• GET /v2/transactions
• GET /v2/transactions/{id}

​

What’s deprecated

• GET /v1/transactions
• GET /v1/transactions/{id}

​

Key changes and improvements

​

Migration and next steps

• All partners using V1 should transition to V2 as soon as possible.
• The V1 endpoint remains operational for now but will be fully sunset at a later date (to be announced).
• If you use V1, update your integrations accordingly and reach out if you need support.