Skip to main content
Network APIs for Connectivity Quality

Implementation Detail

In short
  • What the tools are: example files, tools and configurations for working with CAMARA network APIs, as a client: a browser portal, an MCP server and API collections for Insomnia.
  • What this covers: the repository (rt-camara-examples) as an API consumer, judged against the CAMARA OpenAPI specifications for Dedicated Networks, QoS Booking, QoS Profiles, QoS Provisioning, Quality on Demand and QoS Booking and Assignment, as they stand on the main branch of each API repository. Judged on the main branch of the repository on 2026-10-22.
  • Source of this page: every requirement is split into the cases its text defines; each case was read against the code by one reader and then independently by a second, with a third reading where they disagreed. Cases that need the common CAMARA schemas that were not available (Device, Area and Point), and cases that obligate only the API provider, are not shown as consumer cases.

CAMARA is an open-source project (Linux Foundation, in collaboration with GSMA) that defines portable network APIs, so that an application can request network behaviour through common interfaces rather than operator-specific ones. For what the APIs define, see the Technology page and the Standards. For how to run the tools, see the Tutorials.

What the Reference Tools implement​

  • Dedicated Networks, portal and MCP server: both call the service areas, network profiles, networks and accesses APIs with a client-credentials token, and the portal has a generic webhook receiver for events. They follow an earlier form of the API: one device per access, not a devices list, and list responses read as bare arrays, not as the paged objects (items and pagination) the current specification defines. The network name is kept only as a local label and is not sent.
  • Dedicated Networks, Insomnia collection: the create request sends a devices list, while the add and remove requests send a single device object.
  • QoS Booking, QoS Booking and Assignment, QoS Provisioning and Quality on Demand: these exist as Insomnia requests, with no authentication block and no code that reads a response. The booking create request omits the required serviceArea, the assign request sends device where the API declares devices, the release request uses DELETE where the API defines POST, the extend-session request sends requestedDuration where the API declares requestedAdditionalDuration, and several requests send networkAccessIdentifier, which the specification says is not supported in this version.
  • QoS profiles: the portal retrieves the list and the detail of a profile and shows its top-level properties; nested values appear only as text.
  • Authorisation: only the two-legged client-credentials flow is used; the three-legged cases, and the cases about handling responses and events by name, are absent.

Implementation status​

Open a feature, then a requirement, to see each case and why. Filter by component and release.

  • CAMARA Connectivity Quality Management APIs.
  • API consumer (CAMARA API consumer (Dedicated Networks management portal, Dedicated Networks MCP server, Insomnia collections for Dedicated Networks, QoS Booking and Quality on Demand)): rt-camara-examples.
  • Source: code read against every statement of the specifications on the project page; statements a component cannot meet by construction marked absent by group, 2026-10-22.
  • Not shown: 7 further cases (it could not be settled by reading the code; the readers disagreed, so the case is not shown).
232 of 567 implemented · 30 differ · 305 absentcases, over 206 requirements

✓ Implemented≠ Differs from the specification– Absent? Specification inconsistent: its text and its OpenAPI or tables disagreei Noted: observed, not a verdict against a clause

Event notifications23 of 40 implemented · 17 absent
Dedicated Network - Network Service Areas API17 of 24 implemented · 1 differs · 6 absent
Dedicated Network - Network Profiles API12 of 17 implemented · 1 differs · 4 absent
Dedicated Network - Networks API21 of 28 implemented · 3 differ · 4 absent
Dedicated Network - Accesses API29 of 102 implemented · 11 differ · 62 absent
QoS Booking and Assignment - Device Assignment API2 of 41 implemented · 6 differ · 33 absent
QoS Booking and Assignment - QoS Booking API18 of 69 implemented · 2 differ · 49 absent
QoS Booking API19 of 72 implemented · 2 differ · 51 absent
QoS Profiles API31 of 42 implemented · 11 absent
QoS Provisioning API18 of 54 implemented · 1 differs · 35 absent
Quality on Demand API42 of 78 implemented · 3 differ · 33 absent
Full audit for members

The full audit, with the code behind each verdict, is available to 5G-MAG members through Developer Tools.

Become a member · Request access