Skip to main content
These docs are organised around the platform itself:
  • Components are the platform’s core objects (locations, chargers, tariffs, tokens, sessions), and they map directly to the resources in the API reference.
  • Capabilities are what the platform does with those objects: roaming, billing, energy management, and the rest.
  • Guides put them to work end to end, so you can get started straight away.
Charge point operators (CPOs) and e-mobility service providers (eMSPs) share the same components. A location, a tariff, or a session means the same thing to a CPO and to an eMSP, but each reaches them through different endpoints and features. Capabilities connect the two: roaming, for example, takes a location and tariff a CPO has published and makes them reachable to an eMSP’s drivers, then settles the session between them.

Interfaces

Spirii Connect

The admin web app. Operators manage locations, chargers, pricing, and access; eMSP and fleet admins manage tokens and drivers.

Spirii API

Build the platform’s capabilities directly into your own systems and front-ends.

Spirii Go / branded apps

The driver app (Spirii’s own, or an eMSP’s branded version) for finding, starting, and paying for a charge.

Spirii POS

Spirii’s point-of-sale software for in-person card payments, running on Payter Apollo terminals.

Roles

Charging

Access

Commercial

Where each component is defined

Each object above has its own component page with the full detail: attributes, states, and how it’s used. Capabilities act on these objects, and guides walk you through using them end to end.

Components

The full definitions, one page per object.

Capabilities

What the platform does with these objects: roaming, energy management, billing.

Guides

Start-to-finish walkthroughs to get you up and running.