NexBlue
How Joulo connects a NexBlue charger through the third-party OpenAPI, with OAuth refresh-token rotation.
NexBlue chargers connect through the NexBlue third-party OpenAPI. You sign in with your NexBlue account once, and Joulo keeps the connection alive by rotating the refresh token.
At a glance
| Property | Value |
|---|---|
| Route | Cloud API |
| API | NexBlue third-party OpenAPI |
| Authentication | OAuth 2.0, refresh token with a 30-day lifetime |
| Sync | Every 15 minutes |
| MID detection | Per model, from the Joulo charger catalog |
| Backfill | Automatic, to 1 January 2026 |
How the connection works
Joulo lists your chargers, reads the product name and place data per charger, and pulls sessions per charger. The token endpoint rotates the refresh token on every use, so Joulo writes the new one back immediately.
The session endpoint requires an explicit date range and offers no pagination. Joulo therefore requests history in bounded windows rather than in one call.
What Joulo reads
Sessions come per charger, each with a start time, an end time and the metered energy in kWh.
MID certification
NexBlue exposes no MID flag. Product names are stable strings in the OpenAPI, such as nexblue_edge_max, so Joulo matches the model against its hardware catalog.
The Max line, which covers the Edge Max and the Delta Max, is MID-certified. For any other NexBlue model, check whether a MID meter is built in before you count on ERE registration.
Limitations
- No MID flag from the API. The verdict comes from the catalog.
- A charger removed from your NexBlue account disappears from discovery. Its stored sessions stay in Joulo.