Skip to main content

Monitor charging stations

Feed station health into your own monitoring or NOC tooling. Scope needed: charging-stations:read.

Poll the station list​

curl -s "https://<gateway-host>/api/charging-stations/v1" \
  -H "API-KEY: wsk_..." \
  --get --data-urlencode 'dsquery={"Pager":{"Skip":0,"Take":100},"Sort":{"Sorts":[{"Field":"Name","Dir":"Asc"}]}}'

Each station carries three status dimensions — alert on the right one:

  • NetworkStatus — is the station connected and heartbeating right now? This is your primary availability signal.
  • Status — the administrative state on the platform; a station deliberately taken out of service is not an incident.
  • HardwareStatus — the device's self-reported condition, when the vendor provides one.

The stations you see are your organisation's — tenancy scoping is automatic.

Filter to what matters​

Poll only stations in trouble instead of diffing full snapshots — for example everything not currently online (check the enum's values in the reference and adjust):

{
  "Pager": { "Skip": 0, "Take": 100 },
  "Filter": { "Logic": "And", "Filters": [
    { "Field": "NetworkStatus", "Operator": "Neq", "Value": "1" }
  ]}
}

Polling etiquette​

  • A 1–5 minute interval is plenty; station state doesn't change faster than the heartbeat that reports it.
  • Your key's gateway subscription carries a rate limit — a sane poll never approaches it, but honor 429 + Retry-After anyway.
  • Alert on transitions, not states, and debounce single missed heartbeats: connectivity blips are routine in the field.

Drill into one station​

GET /api/charging-stations/v1/{id} returns the full detail — EVSEs with their own statuses, firmware identity, connectivity metadata — for the incident view your NOC opens when the list flags something.