Wallbox
How Joulo connects a Wallbox charger: Cloud API, authentication, sync cadence and MID detection.
Wallbox chargers connect through the Wallbox API. You sign in with your myWallbox account once. Joulo then reads your charging sessions every 15 minutes.
At a glance
| Property | Value |
|---|---|
| Route | Cloud API |
| API | Wallbox API |
| Authentication | myWallbox account, exchanged for a short-lived JWT |
| Sync | Every 15 minutes |
| MID detection | Per model, from the Joulo charger catalog |
| Backfill | Automatic, to 1 January 2026 |
How the connection works
Wallbox issues JWTs that live about 15 minutes. Joulo holds your account credentials in Supabase Vault and mints a fresh token on each run. Credentials never reach the browser bundle.
If the stored credentials are gone, Joulo marks the integration as expired with a reconnect message rather than retrying a call that cannot succeed.
What Joulo reads
Joulo reads the session list per charger. Each row carries a start time, an end time and the metered energy. Sessions are matched against what Joulo already stored, so a repeated fetch never double-counts.
MID certification
The Wallbox API exposes a midEnabled field, and it is not reliable on its own. The flag flips to false for the duration of a firmware update and back afterwards. Joulo therefore treats a missing MID signal as a weak negative. It can classify a charger that has no verdict yet, and it never demotes a certified one.
Of the current line, only the Pulsar Pro carries a MID meter. The Pulsar Plus, the Pulsar Max and the Commander 2 do not.
Limitations
midEnabledis unreliable during firmware updates. Trust the catalog verdict on the charger object.- A myWallbox account with several homes exposes every charger on it. Link only the chargers on your own connection.