Base URL
REST requests go to the production API:The APIs
The reference covers four APIs. Three are REST: they share the host above, but each sits under its own path prefix, so check the prefix before you build a request. The fourth, the Energy Management API, is asynchronous: you address channels rather than paths, and Spirii provisions those addresses per actor during onboarding.Spirii API
Spirii API
The core platform: locations, EVSEs, charge boxes, tariffs, tokens, vouchers, customers, transactions, and charge records.Example:
https://api.spirii.com/v2/transactionseMSP API
eMSP API
Spirii’s mobility offering, addressed per tenant: tenant profiles, networks, locations, and webhooks.Example:
https://api.spirii.com/emsp/v1/tenant/profileBilling API
Billing API
Reimbursement for home and workplace charging: expense reports and the rates they are calculated against.Example:
https://api.spirii.com/reimbursement/v1/expense-reportsEnergy Management API
Energy Management API
Programmatic Charger Control: external software, typically a third-party energy management system (EMS), reads real-time inputs and sends dynamic power limits to the chargers Spirii controls.Example: the
control-request channel, at an address provisioned per actor.Spirii does not currently offer a separate sandbox environment, so testing is done against production. We recommend connecting a test charger to run your integration tests safely.
Where to next
Authentication
Get an API key and authorize your first request.
Versioning
The current version, version history, and deprecation policy.
Quickstart
A five-minute walkthrough to your first successful request.
Rate limits
The API rate limits and how to work with them.