Extended billable item exports and a public Invoices API
Billable item exports of CPO usage and MSP usage invoices now say exactly what each line bills: a stable fee type, a label, the IDs of the session, token or billing plan behind it, and the quantity, rate or percentage that produced the amount. The same export is available through new public Invoices endpoints, per invoice or for a whole billing period, so a provider that runs its own billing can feed it straight into an ERP or accounting tool.
What changed
- Extended export for CPO usage and MSP usage invoices, as CSV, Excel or NDJSON. Each row carries a stable fee type and a human-readable label, the billed account, and the calculation fields: quantity, rate, calculation type and, for percentage fees, the base amount.
- Session rows include the session ID, the external session ID, start and end time, energy in kWh and the location. CPO rows add the charging station's EVSE ID, OCPP identity and serial number, and the payment flow for payment fees. MSP rows add the token and card identity and, for session usage, the CPO price, its currency and the exchange rate applied.
- Public Invoices API under /2/invoices: search invoices, fetch one invoice, download its PDF, export the billable items of one invoice, and export the billable items of every ready invoice of a type, year and month in one stream. Invoices of child providers are included by default and can be excluded per request.
- Every export row carries the invoice ID and the invoice number, so a billing period export groups back to its invoices.
- The separate CSV and Excel download buttons on invoice menus are merged into one Download Invoice Billable Items action, for account admins and provider admins alike. It offers the content (Extended or Short) and the format.
- An export is complete or not served at all. The API responds 409 while the data behind an invoice is still being completed and 503 when the export cannot be produced; it never returns a partial file. An NDJSON export ends with an end frame that carries the total row count.
The previous billable item export is now labelled Short and marked deprecated. It is unchanged and stays available for now, so automations built on it keep working, but it will be retired at a later stage. Move integrations to the Extended export or to the /2/invoices endpoints. Reimbursement (credit) invoices are not part of this change and keep the Short export.