Charging Groups (beta)

Returns a paginated list of all charging groups for the current provider, without conflict detection. Use it to look up the id of a group you want to associate a charging policy with.

Creates a charging group for the current provider and returns its id, ready to be referenced from a charging policy's associatedChargingGroupIds.

Each entry in filters selects connectors in exactly one way — connectors (a list of chargingStationId + evseId + connectorId), locationIds, or accountIds. Prefer groups that do not overlap: where a connector is covered by more than one group the platform resolves an order internally, but it is not part of this contract.

Returns a paginated list of charging groups for the current provider, filtered by ids, free-text query or creation date range. Alongside the groups, data.conflicts reports groups whose filters overlap — directly (two groups naming the same connector) or indirectly (one group naming an account or location, another naming a connector belonging to it). Use it to find connectors covered by more than one group, since the order in which their policies apply is not something you can control through this API.

Returns a single charging group owned by the current provider, with the filters that select its connectors.

Replaces an existing charging group: the label and the full filters array are overwritten with the values supplied, so filters that are not resent are removed. To add or remove a single connector, location or account without resending the rest, use the filter member endpoints instead. Charging policies associated with the group are unaffected; they simply apply to the new set of connectors.

Deletes a charging group. A group that is still associated with a charging policy cannot be deleted; remove it from the policy first, otherwise the request fails.

Adds a single connector, location or account to an existing charging group, leaving the rest of its filters untouched. Supply exactly one of connector, filterLocationId or filterAccountId.

The member is added to the matching filter if the group already has one, otherwise a new filter is appended. Adding a member that is already present is a no-op, so the call is safe to repeat.

Two naming details differ from create/update and are easy to miss: a connector is identified here by ocppEvseId and ocppConnectorId (evseId and connectorId in the filters array on create/update), and filterLocationId / filterAccountId carry the filter prefix deliberately, because plain locationId / accountId in a request body are intercepted by platform-wide scoping middleware.

Removes a single connector, location or account from an existing charging group, leaving the rest of its filters untouched. Supply exactly one of chargingStationId (together with ocppEvseId and ocppConnectorId), filterLocationId or filterAccountId as query parameters.