They have been vetted for quality, consistency, and stability through rigorous release management processes, the Linux Foundation says
The Linux Foundation’s CAMARA project, “the open source community addressing telco industry API interoperability”, announced its second official release, Meta-release Spring25. It contains 13 new and 23 updated APIs, making 36 in total that have been vetted for quality, consistency and stability.
These APIs are included in the Meta-release:
- Stable CAMARA APIs for Device Reachability Status, Device Roaming Status, Location Verification, Number Verification, One-time Password SMS, QoS Profiles, Quality On Demand, and SIM Swap.
- Updated Versions of existing CAMARA APIs for Applications Profiles, Call Forwarding Signal, Carrier Billing, Carrier Billing Refund, Connectivity Insights, KYC Fill-In, KYC Match, Location Retrieval, Population Density Data, QoD Provisioning, and the updated versions of APIs to subscribe for event notifications: Connectivity Insights Subscriptions, Device Reachability Status Subscriptions, Device Roaming Status Subscriptions, Geofencing Subscriptions, SIM Swap Subscriptions
- Initial versions of new CAMARA APIs, ready to be implemented by network operators for Blockchain Public Address, Connected Network Type (including Subscriptions), Customer Insights, Device Identifier, Device Swap, Know Your Customer Age Verification, Know Your Customer Tenure, Number Recycling, Region Device Count, WebRTC Call Handling, WebRTC Events and WebRTC Registration.
Guidelines
Meta-release Spring25 also includes updated CAMARA design guidelines with improvements to notifications, events and error responses. These changes have been applied by all APIs in the release. The Security and Interoperability Profile has also been revised to make it clearer and with more options for API providers to offer “secure, privacy-friendly and seamless access for developers to network information and capabilities”.
The APIs are organised in 19 different repositories, nine of which were recently promoted by the Technical Steering Committee (TSC) to the “Incubated” stage: Call Forwarding Signal, Device Location, Device Status, Simple Edge Discovery, Number Verification, OTP Validation, Sim Swap, Know YourCustomer, Quality On Demand
Beyond the 10 Sandbox repositories which participated in the meta-release, there are 24 more Sandbox API repositories which is where work on the next wave of CAMARA APIs is underway.
To learn more about all CAMARA’s growing list of API families as well as specific APIs, please visit https://camaraproject.org/api-overview/.
Broad ecosystem support
“The Spring25 Meta-Release marks a…milestone in CAMARA’s mission to drive open, standardized APIs for the global telecom industry,” said Arpit Joshipura, general manager, Networking, Edge and IoT at the Linux Foundation. “We’re continuing to see broad ecosystem support for CAMARA and its innovative APIs that empower developers, accelerate service innovation, and strengthen the ecosystem of open collaboration that is vital for the future of connectivity.”
Nathan Rader, CAMARA Governing Board Chair and VP, Service and Capability Exposure, Deutsche Telekom. “The availability of even more mature, stable telco APIs expands the possibilities for developers and organizations to harness this work more effectively, driving new opportunities across the ecosystem. We look forward to seeing how the industry leverages these enhancements to deliver next-generation services and experiences.”
CAMARA’s background
CAMARA was initiated in 2021 by a group of telcos, vendors and hyperscalers, then officially launched in February 2022 with 22 partners. It graduated to a funded model in September 2023, with 250 participating organisations and over 750 contributors. Since then, the project has grown to more than 1,250 contributors from 427 organisations. It has 11 API sub-projects, 21 sandbox projects, 60 APIs and five working groups. The project says its growth rate indicates “strong ecosystem support in enabling more accessible and standardized open telco APIs”.
The community is committed to delivering updates twice a year to vetted APIs so network operators can plan deployments within their networks
