> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cariqa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-08-21 — v1.1.0

> Context and impact for Cariqa Connect API v1.1.0.

## Overview

This release improves transparency and charging session energy precision.

## Why this was delivered

### Added

1. Added the `sold_by` field to station and charging session details.
   * The Merchant of Record (MoR) is the legal entity that issues the invoice for a charging session.
     In Cariqa's model, the MoR is not always the same as the CPO (Charge Point Operator) visible at the station.
     When a CPO operates through an aggregator, the aggregator acts as the MoR, meaning the end user will receive an invoice from the aggregator, not from the station's CPO brand.
     To ensure transparency, Cariqa surfaces the MoR to the end user via a `sold_by` field, shown on the station page, during an active charging session, on the invoice, and in charging history.

### Changed

1. Updated `consumed_energy` precision from 3 to 4 decimal places.
   * Some CPOs provide more precise energy consumption data.
     Cariqa now surfaces this additional precision so integrations can display charging session energy usage more accurately.

## Impact

Integrations that display invoice issuer information can now use `sold_by`:

* `GET /stations/details/`
* `GET /stations/around/`
* `GET /users/<str:user_id>/charging-sessions/`
* `GET /users/<str:user_id>/charging-sessions/<str:session_id>/`
* `PATCH /users/<str:user_id>/charging-sessions/<str:session_id>/`

Integrations that parse or validate `consumed_energy` might allow up to 4 decimal places.

## Required action

No action is required unless your integration validates `consumed_energy` precision. If so, update validation to accept up to 4 decimal places.

These changes extend existing functionality only.