Description
The Common API Framework (CAPIF) is a cornerstone of 3GPP's service-based architecture, designed to provide a unified, standardized, and secure method for exposing network capabilities to external entities. It functions as an API management layer that sits between the 3GPP core network functions (NFs) and external Application Functions (AFs) or third-party service providers. CAPIF's primary role is to abstract the complexity of the underlying network, offering a consistent, well-defined, and discoverable set of northbound APIs. This allows developers to create applications that leverage network capabilities—such as quality of service (QoS) control, location information, network status, and user authentication—without needing deep knowledge of the proprietary interfaces or internal protocols of the network. The framework is built on RESTful principles, typically using HTTP/2 and JSON, aligning with modern web development practices for ease of adoption.
Architecturally, CAPIF is centered around several key logical functions. The CAPIF Core Function (CCF) is the central entity that provides API publishing, discovery, and registration services. It maintains a repository of available APIs from various API exposing functions. The API Invoker is the client entity (e.g., an external AF) that discovers and invokes APIs after proper authentication and authorization. The API Exposing Function (AEF) is the entity that hosts and exposes the actual network capability APIs, such as a Network Exposure Function (NEF) or a Charging Function. The CAPIF Provider Domain represents the administrative domain that operates the CAPIF framework, typically the mobile network operator (MNO). Security is paramount, managed by the CAPIF Security Function, which handles authentication, authorization, and certificate management for all entities interacting within the framework.
The operation of CAPIF follows a defined lifecycle. First, an API Provider (like an NEF) publishes its API interface details (the API definition, endpoints, and supported operations) to the CCF. An external API Invoker (an application server) then discovers available APIs by querying the CCF. Before invocation, the API Invoker must register with the CAPIF framework and obtain the necessary credentials and access tokens. The CCF and Security Function perform authentication and policy-based authorization to ensure the invoker is permitted to access the specific API. Once authorized, the API Invoker can directly invoke the API on the respective AEF. CAPIF also supports API lifecycle management, including versioning and deprecation, as well as logging and charging for API usage. This managed, secure gateway model prevents unauthorized access to sensitive network functions while enabling controlled and monetizable exposure.
CAPIF's role extends beyond simple API exposure; it is an enabler for network programmability and open innovation. By providing a single, standardized framework, it eliminates the need for bilateral, custom integrations between application providers and each MNO. This reduces development time and cost for third parties and allows MNOs to consistently manage and monetize their network assets. In the context of 5G and network slicing, CAPIF is crucial for allowing vertical industries (e.g., automotive, manufacturing) to request and manage slices or specific network behaviors for their applications through standardized APIs. It thus acts as the bridge that transforms the telecom network from a closed, monolithic system into an open platform for service creation.
Purpose & Motivation
CAPIF was created to address the historical challenge of 'walled gardens' in telecommunications networks. Before its introduction, network capabilities were largely inaccessible or exposed through proprietary, operator-specific interfaces. This made it difficult and expensive for third-party application developers and enterprises to innovate and create services that leveraged real-time network intelligence, such as user location, bandwidth management, or connectivity status. The lack of a common framework resulted in fragmented ecosystems, duplicated development efforts, and slowed the pace of service innovation in the mobile domain.
The primary problem CAPIF solves is providing a standardized, secure, and scalable method for Network Exposure. As 3GPP evolved towards a cloud-native, service-based architecture (SBA) with 5G, the need for a formalized exposure layer became critical. CAPIF provides this layer, defining the common rules, security procedures, discovery mechanisms, and lifecycle management for all northbound APIs. This solves the integration complexity problem, allowing an application written for one operator's network to more easily work with another's, fostering a healthier application ecosystem.
Furthermore, CAPIF enables new business models for Mobile Network Operators (MNOs). By offering a controlled and billable gateway to network capabilities, MNOs can monetize their network assets beyond basic connectivity. It empowers vertical industries participating in the 5G economy—like IoT, automotive, and media—to directly interact with the network to fulfill their specific requirements for low latency, high reliability, or massive device connectivity. In essence, CAPIF is the technological foundation that allows the 3GPP network to become a true platform-as-a-service (PaaS), driving innovation and creating new revenue streams in the 5G era.
What changed in its specifications
The latest release-to-release comparison of specifications that define CAPIF. Each summary describes the whole specification, not only this term.
Rel-19 adds CAPIF Phase 3 procedures for unpublishing service APIs between interconnected core functions, revoking API invoker and resource owner authorization, open discovery of service APIs, and UE-hosted API invoker access to resources owned by other UEs.
Full comparison in TS 23.222 →Rel-19 added real-time flight path reporting, QoS-based flight route selection, no-transmit zone management, and supporting APIs/procedures for UAS applications.
Full comparison in TS 23.255 →Technology family
Network exposure and analytics · Core Network
- Rel-11 SCS/AS
- Rel-13 IWK-SCEF, SCEF
- Rel-15 CAPIF, NEF, NWDAF
- Rel-16 SCEF+NEF
- Rel-17 ADRF, AnLF, DCCF, L-NEF, MDAF, MFAF, MTLF
- Rel-18 RE-NWDAF
- CAPIF used together with SCEF
“The SCEF may support CAPIF. When CAPIF is supported, the SCEF supports the CAPIF API provider domain functions.” TS 23.682
- CAPIF used together with NEF
“When an NEF is used for external exposure, the CAPIF may be supported. When CAPIF is supported, an NEF that is used for external exposure supports the CAPIF API provider domain functions.” TS 23.501
Members and relations were proposed independently by several models and kept only where at least two agree; quotes are verified verbatim against the specifications. Release = first approved version of the defining specification.
Release Timeline
Detected Changes Across Releases
verified against 3GPP sourcesDocumented changes in 6 releases, each verified against the text of 3GPP specifications or approved change requests and shown with the exact wording. The release timeline above shows the same releases. A release without an entry has no documented change for this term.
CAPIF is specified for the first time in Rel-15: stage 2 architecture and requirements in TS 23.222, protocol APIs in TS 29.222, and security architecture in TS 33.122.
- “The present document specifies the architecture, procedures and information flows necessary for the CAPIF.” TS 23.222 v15.7.0
- “The present document specifies the APIs needed to support CAPIF.” TS 29.222 v15.15.0
- “The present document specifies the security architecture i.e., the security features and the security mechanisms for the common API framework (CAPIF)” TS 33.122 v15.4.0
CAPIF was extended in Rel-16 with interconnection between CAPIF providers, 3rd party trust domain support, new CAPIF-3e/4e/5e/6/6e/7/7e reference points and related requirements.
- “CAPIF-6 and CAPIF-6e reference points connect two CAPIF core functions located in the same or different PLMN trust domains, respectively.” TS 29.222 v16.14.0
- “The CAPIF shall provide mechanisms to enable the API invokers of the CAPIF provider to discover and invoke the service APIs of the 3rd party CAPIF provider.” TS 23.222 v16.13.0
- “CAPIF-3e reference point connects an API exposing function outside PLMN Trust Domain with the CAPIF core function.” TS 29.222 v16.14.0
CAPIF gained Serving Area Information support for service APIs and discovery criteria, and its stage-2 architecture was restructured as service-based with a Cccf interface; stage-3 APIs received corrections.
- “The CAPIF shall provide mechanism to support Serving Area Information related to service APIs.” TS 23.222 v17.8.0
- “The CAPIF architecture contains the following service-based interfaces:” TS 23.222 v17.8.0
- Support redirection and mandatory error codes for CAPIF APIs TS 29.222CR0207
CAPIF gained new capabilities in Rel-18: support in SNPN, RNAA-based resource owner authorization, extensibility requirements, and CAPIF core function interconnection with peer publishing via a published API path.
- “CAPIF supports RNAA and has enabled API invoker(s) to have authorized access to resources of a resource owner provided by service APIs offered by the AEF.” TS 23.222 v18.10.0
- “The CAPIF shall be extensible to support different protocol stack models, including related security mechanisms, in addition to the minimum common protocol stack model.” TS 23.222 v18.10.0
- Support CAPIF in SNPN TS 23.222CR0109
CAPIF gained interconnection between CAPIF providers via CAPIF-6/6e, new requirements for 3rd party CAPIF providers and resource owner authorization, and revised Events service behaviour including new CAPIF_Ext1 events.
- “The CAPIF shall provide mechanisms to enable a CAPIF provider to publish, retrieve unpublish and update service APIs in a 3rd party CAPIF provider.” TS 23.222 v19.10.0
- “CAPIF-6/6e interfaces are interconnecting two CAPIF core functions.” TS 33.122 v19.4.0
- “if the "CAPIF_Ext1" feature is supported and the event is "SERVICE_API_ONBOARDED_BY_API_INVOKERS_COUNT"” TS 29.222 v19.8.0
CAPIF gained a second set of enhancements in Rel-20: extended event reporting (eventReqExt), updated API provider management operations, service API analytics, and resource-owner/purpose-based authorization by the CAPIF core function.
- “If the "CAPIF_Ext2" feature is supported, the Subscriber may also include the "eventReqExt" attribute within the EventSubscription data structure” TS 29.222 v20.1.0
- “The CAPIF may provide the mechanisms to enable the service API analytics for the API providers.” TS 23.222 v20.1.0
- New Disenroll_Service_APIs service operation in CAPIF_API_Provider_Management_API TS 29.222CR0480
Defining Specifications
3GPP specifications that define or reference CAPIF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 22.832 vh40 | Study on cyber-physical control in vertical domains | Rel-17 read |
| TS 23.222 vk10 | Common API Framework (CAPIF) | Rel-20 read |
| TS 23.255 vk10 | UAS Application Enabler Architecture | Rel-20 read |
| TS 23.286 vk10 | V2X Application Enabler Architecture | Rel-20 read |
| TS 23.433 vk40 | SEAL Data Delivery Architecture | Rel-20 read |
| TS 23.434 vk10 | Service Enabler Architecture Layer (SEAL) for Verticals | Rel-20 read |
| TS 23.438 vk30 | Digital Asset Service for Mobile Metaverse | Rel-20 read |
| TS 23.501 vk30 | 5G System Architecture | Rel-20 read |
| TS 23.554 vj80 | MSGin5G Service Application Architecture | Rel-19 read |
| TS 23.558 vk30 | Enabling Edge Applications | Rel-20 read |
| TS 23.700 vk10 | AI/ML Application Layer Support Phase 2 | Rel-20 read |
| TS 23.722 vf10 | Common API Framework (CAPIF) for 3GPP Northbound APIs | Rel-15 read |
| TR 23.745 vh00 | Study on App Layer Support for Factories of the Future in 5G | Rel-17 read |
| TR 23.758 vh00 | Study on Edge Application Architecture | Rel-17 read |
| TR 23.764 vh10 | Study on V2X Application Layer Enhancements | Rel-17 read |
| TR 23.958 vj00 | EDGEAPP alignment with ETSI MEC and GSMA OP | Rel-19 read |
| TS 24.538 vj40 | MSGin5G Service Protocol Specification | Rel-19 read |
| TS 24.560 vk10 | AIMLE SEAL Services Stage 3 | Rel-20 read |
| TS 26.501 vk00 | 5G Media Streaming Architecture | Rel-20 read |
| TS 26.531 vj00 | Data Collection & Reporting Architecture for 5G | Rel-19 read |
| TS 26.891 vg00 | Media Distribution Services in 5G System | Rel-16 read |
| TS 28.849 vj10 | CAPIF Phase2 Charging Study | Rel-19 read |
| TS 28.879 vj10 | OAM for Service Management Exposure Study | Rel-19 read |
| TS 29.116 vj00 | REST-based protocol for xMB reference point | Rel-19 read |
| TS 29.122 vk10 | T8 SCEF Service Exposure APIs | Rel-20 read |
| TS 29.222 vk10 | CAPIF Northbound API Protocol | Rel-20 read |
| TS 29.486 vj40 | V2X Application Enabler (VAE) Protocol; Stage 3 | Rel-19 read |
| TS 29.522 vk10 | NEF Northbound Interface | Rel-20 read |
| TS 29.538 vk00 | MSGin5G Service API Stage 3 | Rel-20 read |
| TS 29.558 vk00 | Edge Application Enablement APIs | Rel-20 read |
| TS 32.254 vk00 | 3GPP TS 32.254: Charging for Northbound APIs | Rel-20 read |
| TS 32.291 vk10 | 5G Charging Service-Based Interface | Rel-20 read |
| TS 32.298 vk10 | Charging Data Record Specification | Rel-20 read |
| TS 33.122 vj40 | CAPIF Security Architecture Specification | Rel-19 read |
| TS 33.519 vk10 | NEF Security Assurance Requirements and Tests | Rel-20 read |
| TR 33.884 vi01 | Technical Report | Rel-18 read |