By 
In today’s business landscape, optimizing operations and providing excellent user experiences are crucial. Network APIs play a key role in achieving this by opening up networks and allowing companies to optimize their applications. For telecom companies, network APIs provide an opportunity to monetize their networks and offset high investments in infrastructure. This creates a win-win situation for both customers and operators.
Several key initiatives have been established to make this a reality:
📹 Going on record for 2026? We're recording the TFiR Prediction Series through mid-February. If you have a bold take on where AI Infrastructure, Cloud Native, or Enterprise IT is heading—we want to hear it. [Reserve your slot
- Standardization of APIs: This is where the Linux Foundation’s CAMARA project comes in, helping define and develop network APIs.
- Standardization of operator API exposure: GSMA’s Open Gateway initiative works to standardize how operators expose APIs.
- API aggregation: A newly announced company, “API Venture,” is focusing on aggregating APIs globally.
CAMARA is tasked with creating standardized APIs, while GSMA Open Gateway focuses on distribution channels, business models, and making it easier for operators to implement these APIs. The Open Gateway initiative has garnered widespread support, with over 55 operators signing on, while CAMARA has over 390 member companies collaborating to streamline network API development. In September 2024, leading telcos formed “API Venture” to provide global APIs with standardized technical and commercial frameworks, supporting data usage rights management and developer platforms.
What is CAMARA?
CAMARA is a collaborative project involving telecommunications operators and industry players to create standardized APIs for network services. It operates under the Linux Foundation and aims to allow faster, more consistent development of network-aware applications across multiple telecom operators, addressing the industry’s fragmented nature.
Historically, each operator had its own unique set of APIs, which made it difficult for developers to create applications that worked seamlessly across different networks. CAMARA’s standardization effort allows applications to interact with telecom networks in a unified manner.
What are API categories that CAMARA addresses?
CAMARA covers telecom APIs related to mobile, fixed-line, and other network services. Key business areas include fraud prevention, location services, and enhanced communication capabilities.
Can you talk about the Release Management process and why its important?
CAMARA has implemented a robust release management process to ensure API versions meet quality standards. This process guarantees that APIs are consistent, reliable, and ready for developers to use in real-world applications. This ensures the availability of consistent API definitions, the quality of API definitions (through checklists and test definitions), the stability of API definitions (with clear criteria for stable versus initial API versions), and the reliability of schedules and deliverables (with defined milestones and release candidates).
CAMARA recently issued its first major, “Meta” release – can you tell us about that?
With its first major release, CAMARA is working closely with customers and developers to create high-value APIs that serve real-world demands. The focus now shifts to evolving these APIs to be more intent-based, directly addressing customer needs.
What are some example Use Cases of CAMARA-based APIs?
Some of the most widely used CAMARA APIs focus on fraud prevention, including SIM Swap and Number Verification services, which are crucial for securing network operations.
What are the opportunities for Aggregators, Vendors, and Hyperscalers to get involved with open network APIs?
- Aggregators can simplify network integration by using CAMARA APIs, reducing the complexity and cost of connecting to multiple operators while expanding service offerings.
- Vendors can leverage these APIs to build solutions compatible with various operators, facilitating faster innovation and deployment.
- Hyperscalers can extend cloud services into operator networks, enabling hybrid cloud and edge computing solutions. By partnering with telecom operators, they can offer combined services like managed IoT platforms or low-latency compute solutions.
What is CAMARA’s role in Cloud-Native environments?
CAMARA’s abstraction layer allows cloud-native applications to utilize advanced network capabilities, such as quality of service (QoS) and edge computing, without requiring in-depth telecom knowledge. This helps developers create applications that perform well across different networks and cloud environments. CAMARA also supports Cloud Native Network Functions (CNFs) and works with tools like Kubernetes, facilitating seamless integration and deployment across hybrid and multi-cloud infrastructures.
What’s the difference between CAMARA and the Linux Foundation’s OpenAPI project?
CAMARA and the Linux Foundation’s OpenAPI project serve different purposes. While CAMARA focuses on telecom-specific network APIs, OpenAPI provides a framework for designing and documenting RESTful APIs across industries. CAMARA’s goal is to abstract complex telecom functions, making it easier for developers to integrate network services into their applications, particularly in the context of 5G and cloud computing.
How can someone get involved?
CAMARA invites both developers and operators to participate in shaping the future of network APIs. Developers can help define needed APIs, while operators can contribute by deploying API infrastructure within their networks. Hyperscalers and aggregators are also encouraged to join the effort, leveraging CAMARA APIs to create innovative cloud services.
Interested in learning more about CAMARA? Stop by Booth R48 at KubeCon NA to speak with an expert or see a demo!
To learn more about Kubernetes and the cloud native ecosystem, join us at KubeCon + CloudNativeCon North America, in Salt Lake City, Utah, on November 12-15, 2024.
