Network APIs
Network APIs cover how operator capabilities are exposed to developers through platforms such as Nokia Network as Code and CAMARA-aligned interfaces. The exam tests API exposure architecture, authentication and consent, service mapping to core policy, and the difference between telco-specific and CAMARA APIs.
API exposure architecture
An API gateway or exposure platform authenticates developers, applies quotas, and maps API requests to network functions. CAMARA provides common service APIs; the NEF exposes 3GPP capabilities. OAuth2 is used for delegated authorization, and consent must be captured for privacy-sensitive data such as device location. A QoS-on-demand request must be translated into policy at the PCF and enforced at the SMF/UPF. Charging and event notification are part of the service contract, not optional extras.
Rules to apply
- API keys identify an application; OAuth2 tokens authorize a user or client with scopes.
- Consent is required before exposing subscriber location or other personal data.
- CAMARA APIs are common industry APIs; NEF APIs are 3GPP-defined exposure interfaces.
- QoS on demand changes policy and enforcement; it is not a billing-only action.
- API latency and availability are part of the service architecture.
Worked example
A video application requests temporary QoS for a user session. The app calls a CAMARA QoS-on-demand API through the exposure platform. The platform validates the OAuth2 token and consent, maps the request to a policy decision at the PCF, and the SMF/UPF enforces the QoS flow. Charging records the session. The reasoning: the API is a contract that traverses authorization, policy, enforcement, and charging.
Traps that cost marks
Confusing API keys with OAuth2 authorization; exposing location without consent; assuming every API is CAMARA-defined; and treating QoS on demand as a policy-free upgrade.