Snapshot
Full station state snapshot. The primary way to read all data at once.
Retrieve full station snapshot
Returns the complete state of the charging station as a nested JSON object. The response includes device information, SECC port data, metering, and all configurable parameters.
Use ?path= to navigate to a specific subtree:
GET /api/?path=secc/port0/salia/chargemode→"eco"GET /api/?path=secc/port0/metering→ full metering subtreeGET /api/?path=device→ device information only
Use ?reset to force a fresh read from the MQTT broker (slower, ~2s).
query Parameters
pathSlash-separated path to navigate into the JSON response tree.
Example: secc/port0/salia/chargemode
resetIf present (any value or empty), forces a fresh MQTT read instead of returning the cached snapshot. Slower but guarantees up-to-date data.
Retrieve full station snapshot › Responses
Snapshot retrieved successfully
Static device identifiers
seccSECC port data — charging state, metering, configuration
Write one or more configuration values
The single write endpoint for the API. All PUT/POST traffic is
directed here — sub-path PUT URLs documented elsewhere in this spec
are not independent routes, they are descriptions of topics that
can be included in this endpoint's body.
The request body is a JSON object where each key is an MQTT topic path
(without the port0/ prefix) and the value is the string to publish.
Only whitelisted topics are accepted. Unknown topics are silently
ignored; the overall response is still {"result":"ok"}. There is no
per-topic error reporting.
Multiple values can be set in one request (each is published independently — they are not atomic):
Code
Write one or more configuration values › Responses
Values written successfully
result