JouloDocs

Energy

Monthly energy aggregates and lifetime statistics in Joulo

The energy endpoint provides a high-level view of your charging activity • monthly breakdowns and lifetime totals across all your chargers.

Energy statistics object

{
  "total_kwh": 2847.52,
  "total_ere_credits": 947.21,
  "total_sessions": 186,
  "months": [
    {
      "month": "2026-04",
      "kwh": 124.30,
      "ere_credits": 41.36,
      "sessions": 8
    },
    {
      "month": "2026-03",
      "kwh": 387.45,
      "ere_credits": 128.88,
      "sessions": 22
    }
  ]
}

Top-level fields

FieldTypeDescription
total_kwhnumberLifetime total energy charged across all chargers, in kWh.
total_ere_creditsnumberLifetime total Emissiereductie-eenheden (ERE count), derived from kwh via the NEa formula. Multiply by ere_price_mid from GET /me and (1 − effective_fee_pct/100) to get net euros.
total_sessionsnumberLifetime total number of charging sessions.
monthsarrayMonthly breakdown, sorted newest first.

Monthly fields

FieldTypeDescription
monthstringMonth in YYYY-MM format.
kwhnumberTotal energy charged in this month, in kWh.
ere_creditsnumberTotal ERE count for the month: kwh × 0.505 × 0.6588 (NL renewable fraction × RED III reduction factor).
sessionsnumberNumber of charging sessions completed in this month.

ERE position

Where the energy object tells you how many ERE you generate, the GET /ere-position endpoint tells you what happens to them commercially for a given compliance year • how much is already sold and paid out, reserved, still payable, and the forecast value of what is still unsold.

Joulo sells ERE in batches on the market, so your realised price differs from the indicative one and settles per quarter. The response splits your position into paid, payable, reserved and unsold (with a year-to-date vs. rest-of-year forecast), plus a quarters array with the ERE produced and the ERE sold per quarter • the same reserve/sell/forecast view as the dashboard. Pass ?year= to look at a specific compliance year (defaults to the current one).

See the ERE position reference for the full response shape.

Use cases

Next steps