> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> The four APIs that make up the Spirii Public API, their path prefixes, and where to start.

The Spirii Public API is a set of APIs for managing EV charging infrastructure and e-mobility services on the Spirii platform.

## Base URL

REST requests go to the production API:

```
https://api.spirii.com
```

Every REST endpoint in this reference ships with a request/response schema, parameter list, and an interactive **Try it** playground.

## 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.

<AccordionGroup>
  <Accordion title="Spirii API" icon="sparkles">
    The core platform: locations, EVSEs, charge boxes, tariffs, charge keys, vouchers, customers, transactions, and charge records.

    Example: `https://api.spirii.com/v2/transactions`
  </Accordion>

  <Accordion title="eMSP API" icon="car">
    Spirii's mobility offering, addressed per tenant: tenant profiles, networks, locations, and webhooks.

    Example: `https://api.spirii.com/emsp/v1/tenant/profile`
  </Accordion>

  <Accordion title="Billing API" icon="landmark">
    Reimbursement for home and workplace charging: expense reports and the rates they are calculated against.

    Example: `https://api.spirii.com/reimbursement/v1/expense-reports`
  </Accordion>

  <Accordion title="Energy Management API" icon="bolt">
    [Programmatic Charger Control](/capabilities/energy-management/energy-management#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.
  </Accordion>
</AccordionGroup>

Each API is versioned independently. See [Versioning](/developers/versioning) for the current version of each and where it sits in the path.

<Note>
  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.
</Note>

## Where to next

<Columns cols={2}>
  <Card title="Authentication" icon="key-round" href="/developers/authentication">
    Get an API key and authorize your first request.
  </Card>

  <Card title="Versioning" icon="git-branch" href="/developers/versioning">
    The current version, version history, and deprecation policy.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/developers/quickstart">
    A five-minute walkthrough to your first successful request.
  </Card>

  <Card title="Rate limits" icon="gauge" href="/developers/rate-limits">
    The API rate limits and how to work with them.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.