Getting started
The Woltti platform API gives your systems programmatic access to the charging network your organisation runs on Woltti: charging sessions and stations, tariffs, locations, users and teams, energy assets, billing data and the audit trail.
Base URL and environments
All traffic goes through the Woltti API gateway — your Woltti contact provides the gateway base URLs for the test and production environments when your organisation is onboarded. Develop against test first; the two environments are structurally identical.
Get an API key
API access is a licensed feature. Once your organisation holds the license:
- A CompanyAdmin signs in to the Woltti operator portal and opens Administration → API keys.
- Create API key: name it after your integration, pick a role, and grant the scopes it needs.
- The key is shown once. Store it in your secret manager immediately — Woltti keeps only a fingerprint and cannot show it again.
Full details in Authentication.
Your first call
Send the key in the API-KEY header. This lists your ten most recent charging sessions:
curl -s "https://<gateway-host>/api/charging-sessions/v1" \
-H "API-KEY: wsk_..." \
-H 'Content-Type: application/json' \
--get --data-urlencode 'dsquery={"Pager":{"Skip":0,"Take":10},"Sort":{"Sorts":[{"Field":"StartedAtUtc","Dir":"Desc"}]}}'
A successful response is a paged envelope:
{
"Items": [ { "Id": 12345, "Status": 4, "EnergyConsumed": 21.4, "...": "..." } ],
"TotalCount": 8231
}
If you get 401, the key is wrong or revoked. If you get 403 with an error code, read it — it tells you whether the problem is a missing scope or a lapsed license.
Where to go next
- Authentication — keys, scopes, JWT for user-context flows
- Core concepts — the response envelope and the platform's conventions
- Querying lists with dsquery — filtering, sorting and paging on every list endpoint
- Guides — complete tasks in curl
- API reference — every endpoint, with its required scope