Welcome to the Solidstudio EMSP Public API

Guides and reference pointers for integrating with the back office of the Solidstudio EMSP platform over REST.

The Public API gives external integrators access to the EMSP back office. It covers charging sessions and CDRs, payments and settlement, customers and tokens, the roaming charging network, tariffs, coupons and bulk operations. It is built for host-to-host integration between your backend and the EMSP platform: ERP and accounting sync, customer-care tooling, reporting and fleet management.

Base URL and versioning

All Public API routes live under:

https://<your-environment-host>/backoffice/<resource>

Each resource has its own version, set in the path:

Use the highest version available for a resource. Deprecated endpoints are left out of the Public API specification, and these guides do not describe them.

Quick start

curl -s \
  -H "Authorization: $API_KEY" \
  "https://<host>/backoffice/sessions?page=1&size=10"

{
  "content": [ { "chargingSessionId": "3f1c2a9e-...", "chargingSessionStatusV2": "ACTIVE", "...": "..." } ],
  "totalElements": 116,
  "totalPages": 12,
  "currentPage": 1
}

See Authorization for how to get a key and what it can access.

Conventions

The full rules, including the exceptions, are in Pagination, filtering & errors. In short:

• Content type. Requests and responses are JSON (Content-Type: application/json). Unknown request properties are ignored. A few report endpoints return CSV.
• Pagination. Most list endpoints take page (1-based, default 1) and size (default 10). They return { "content", "totalElements", "totalPages", "currentPage" }. The maximum size depends on the endpoint (100 or 1000, and some have no limit).
• Filtering. Simple lists take query parameters. Charging pools, points and connectors use POST .../query with a JSON filter body. Several resources have a GET .../filters endpoint that returns the allowed filter values.
• Dates. ISO-8601. Query parameters are mostly local date-times interpreted as UTC (2026-10-01T00:00:00). JSON bodies of the v3 queries take offset date-times (2026-10-01T00:00:00Z).
• Errors. { "code": "BAD_REQUEST", "message": "..." }. Validation errors add context.errors[] with field and reason.

Resource catalog

Paths are relative to https://<host>. The Guide column links to the usage page.

Sessions & CDRs

Payments & settlement

Customers & tokens

Charging network

Hierarchy: charging pool (location) → charging point (EVSE) → connector (plug).

Tariffs & coupons

Bulk operations

Platform

These resources have no dedicated guide. See Swagger for their fields.

Usage guides

• Authorization
• Pagination, filtering & errors
• Sessions & CDRs
• Payments & settlement
• Customers & tokens
• Charging network
• Tariffs & coupons
• Bulk operations