[API Proposal] Group Management API

[gmuratk]

Description

The Group Management API enables API Consumers to create and manage named groups of pre-defined entities (e.g. devices or areas).
Currently, across CAMARA sub-projects (CQM family, Device Status, IoT Network optimization, and various Subscription-APIs, etc.), resource supports only a single device, represented by MSISDN, IP address, etc.).
This works for basic use cases, for one-to-one operations, but real-world use cases increasingly require APIs to operate on multiple devices or logical collections of devices.
Use cases

Example Scenarios: API Consumer, customer of an Operator, with service offering impacting huge number of devices connecting to the Operator's network.

• A logistics company with large number of vehicles and processing centers
• An environmental data collection company with fleet of IoT devices
• A Bank with many subscribers

Related to

Related Issue: Standardize Group Management for CAMARA Sub-Projects
Supporting material

cc: @shilpa-padgaonkar

[albertoramosmonagas]

Hi all — following the note in the Commonalities section of the TSC minutes (18 Dec 2025) referencing the related API Backlog item (Group Management API – APIBacklog issue #288), a quick clarification on next steps:

The API Backlog discussion will be deferred to the next session. It is expected that, before the topic is brought to API Backlog for decision, the initial discussions in Commonalities are concluded and a clear, agreed approach is produced (scope, semantics, and impact across APIs), so that API Backlog can assess the proposal based on a consolidated Commonalities outcome rather than an open-ended draft. This reflects the TSC conclusion and intended sequencing.