PAiCore TechnologyLet’s talk ↗

The Rise of Network APIs: Why Telecom Networks Are Becoming Programmable

The Rise of Network APIs: Why Telecom Networks Are Becoming Programmable

By PAiCore Technology ● 4 min read

Telecom networks have always contained valuable capabilities — from subscriber identity and authentication to location, connectivity, and other network services. Historically, however, accessing these capabilities required specialised telecom integrations and knowledge of protocols such as SS7, MAP, and Diameter.

Network APIs are changing that model.

Network APIs provide a modern interface through which applications, enterprises, and digital platforms can access selected capabilities of mobile networks. Instead of requiring every application developer to understand telecom signaling, network capabilities can increasingly be exposed through standardised API interfaces.

The industry is moving toward a common ecosystem around GSMA Open Gateway and CAMARA, with operators, technology providers, and aggregators working toward more interoperable Network APIs.

According to GSMA, Network APIs are helping transform mobile networks into programmable platforms, with applications across areas such as identity verification, fraud prevention, location services, and other network-enabled services.

From Connectivity to Programmable Network Services

The significance of Network APIs goes beyond simply providing another interface.

Traditionally, mobile networks were largely consumed through telecom-specific systems. Applications often depended on intermediaries, proprietary interfaces, or complex integrations to access network capabilities.

The Network API model introduces another layer:

Application → API → Network Capability

This allows selected capabilities already available within an operator’s infrastructure to become services that applications can consume.

Across the broader Network API ecosystem, examples include:

  • Number Verification
  • SIM Swap
  • Location Verification
  • Location Retrieval
  • Geofencing
  • Device information
  • Silent Authentication
  • Quality on Demand

The availability of individual capabilities varies by operator, platform, and implementation. The GSMA Open Gateway portfolio includes a broad range of Network APIs, with the underlying API specifications developed through the CAMARA project.

Why Standardisation Matters

A major challenge for Network APIs is interoperability.

If every operator exposes a network capability differently, an enterprise wanting to deploy across multiple markets can still face multiple integrations.

This is why GSMA Open Gateway and CAMARA are important.

CAMARA, hosted by the Linux Foundation, develops open and standardised Network API specifications, while GSMA Open Gateway provides the broader industry framework for making network capabilities available through common APIs.

GSMA is also developing technical realisation guidelines covering areas such as API routing, consent, onboarding, service consumption, and operational integration.

The objective is straightforward:

Standardise the API experience while allowing operators to retain their underlying network infrastructure.

The Network API Gateway: Connecting APIs to Telecom Signaling

Standardised APIs solve the northbound application interface problem. They do not, by themselves, remove the complexity of the network underneath.

An operator may still have infrastructure based on technologies such as SS7/MAP, SIGTRAN, and Diameter, together with network functions and subscriber infrastructure such as HLR/AuC and 3GPP AAA.

This is where a Network API Gateway becomes an important architectural component.

The PAiCore Network API Gateway bridges modern HTTP/API applications with carrier-grade telecom signaling through SS7/MAP and Diameter. Its event-driven architecture supports protocol interworking and asynchronous telecom workflows. The platform also provides containerised deployment, high availability, load balancing, fault tolerance, and validated throughput of 9,000 TPS under sustained load testing.

The gateway can therefore act as the bridge between:

Modern Applications → REST/HTTP → Network API Gateway → SS7/MAP or Diameter → Mobile Network

This approach allows operators and technology providers to modernise access to network capabilities without requiring every application to implement telecom signaling protocols.

PAiCore and CAMARA Network APIs

The PAiCore Network API Gateway currently provides access to selected network capabilities through CAMARA-aligned APIs.

These include:

Location Retrieval
 Retrieve the area where a specific mobile device is located.

Location Verification
 Determine whether a mobile device is within a specified geographical area.

Geofencing Subscriptions
 Create subscriptions that provide notifications when a mobile line enters or exits a predefined geographical area.

Number Verification
 Confirm ownership of a mobile phone number and retrieve the number directly from the user’s device.

Know Your Customer Age
 Check whether a subscriber is above a specified age threshold. This capability is listed by PAiCore for Q3 2026.

PAiCore’s event-driven architecture also enables use cases such as Silent Network Authentication (SNA) through standard APIs.

Where Network APIs Are Heading

The industry is moving beyond experimentation toward broader commercial deployment.

For operators, the opportunity is to turn selected network capabilities into programmable services.

For enterprises, Network APIs can provide new sources of trusted network information and functionality.

For developers, they offer a simpler way to consume network capabilities without implementing telecom signaling protocols themselves.

And for infrastructure providers, the challenge is to connect the standardised API world with the complex signaling environment that already exists.

That is the role of the Network API Gateway: making network capabilities accessible through modern APIs without requiring the underlying telecom network to be rebuilt.

Explore PAiCore Network API Gateway

The PAiCore Network API Gateway provides multi-protocol interworking between REST/HTTP, SS7/MAP, and Diameter, together with selected CAMARA-aligned Network API capabilities.

Explore the PAiCore Network API Gateway product page

The Network API Gateway is also available as an open-source project for developers, integrators, and telecom engineers exploring modern telecom signaling architectures.

Explore PAiCore open-source repositories

Standards and Industry References

The Network Is Becoming Programmable

Network APIs are becoming a new interface to mobile network capabilities.

The next phase of telecom innovation will depend not only on defining standardised APIs, but also on how effectively those APIs connect modern applications with the network infrastructure and capabilities already in place.

The API is the interface.
The gateway is the bridge.
The network remains the foundation.



Read more at…

RELEASE NOTES

Network API Aggregation: Why Developers Want One Integration Across Multiple Operators

Network API Aggregation: Why Developers Want One Integration Across Multiple Operators

By PAiCore Technology ● 2 min read

One of the biggest opportunities in the Network API ecosystem is reducing the complexity of integrating with multiple mobile operators.

For a developer building a global application, integrating separately with every operator can create significant technical and operational overhead. Different API implementations, onboarding processes, and network environments can make global deployment difficult.

The emerging model is different:

One integration → Multiple operators → Multiple markets

What Is Network API Aggregation?

Network API aggregation brings APIs from multiple mobile operators together through a common access layer.

Instead of building individual integrations with each operator, developers and enterprises can access network capabilities through a single integration point.

This model is becoming increasingly important. The GSMA Intelligence Open Gateway State-of-the-Market Report, H1 2026 identifies aggregation platforms as an increasingly important route to market for Network APIs, noting that developers prefer a single integration point with broader reach.

This supports the broader objective of GSMA Open Gateway and CAMARA: making network capabilities more consistent and accessible to developers.

Does Aggregation Remove Network Complexity?

Not entirely.

A common API interface sits above operator-specific infrastructure. Underneath, networks may still use combinations of:

SS7/MAP | Diameter | HLR/AuC | HSS | AAA

This creates a need for reliable interworking between the standard API layer and the underlying telecom network.

A Network API Gateway provides that bridge.

The Role of a Network API Gateway

The PAiCore Network API Gateway supports HTTP/REST integration with telecom signaling environments including SS7/MAP and Diameter, providing multi-protocol interworking and transaction correlation.

The resulting architecture can be viewed as:

Developer → Aggregator/API Layer → Network API Gateway → Operator Network

This approach allows developers to work with a common API layer while the gateway handles the complexity of communicating with the underlying telecom infrastructure.

From One Integration to Multiple Networks

The industry is moving toward a model where developers can:

Integrate once → Reach multiple networks → Scale across markets

At the same time, operators can retain their existing network infrastructure while making selected capabilities available through standardised Network APIs.

This combination is important for scaling Network APIs across markets:

Standardised APIs above.
 Protocol-aware infrastructure below.
 Reliable interworking between the two.

Explore PAiCore

Learn more about the architecture, capabilities, and deployment options of the PAiCore Network API Gateway:

Explore the PAiCore Network API Gateway product page 

Developers and telecom engineers can also explore the open-source project:

PAiCore Network API Gateway open-source project  

References

Network API aggregation can simplify the path from individual operator integrations to global network access.

By combining standardised APIs, aggregation, and protocol-aware gateway infrastructure, developers can move closer to the goal of one integration across multiple operators and markets.

Read more at…

RELEASE NOTES

From Network API Specification to Production: What Operators Need to Connect APIs to the Network

From Network API Specification to Production: What Operators Need to Connect APIs to the Network

By PAiCore Technology ● 3 min read

Standardising a Network API is an important first step. Deploying that API reliably within a real telecom environment requires another layer of architecture.

A production Network API platform needs to connect applications and developers to existing operator network infrastructure while maintaining security, policy, scalability, and reliable transaction processing.

What Does a Production Network API Architecture Look Like?

A simplified architecture can be represented as:

Application → API → Policy & Security → Network API Gateway → Telecom Signaling → Network Functions

The northbound interface can use standardised Network APIs developed through the CAMARA ecosystem and exposed through frameworks such as GSMA Open Gateway.

GSMA describes Open Gateway as a global framework of common Network APIs designed to provide developers and cloud providers with consistent access to mobile operator networks.

The southbound environment can be considerably more complex.

Depending on the operator and network function, existing infrastructure may include:

SS7/MAP | SIGTRAN | Diameter | HLR/AuC | HSS | AAA

Why the Gateway Matters

A Network API Gateway provides the interworking layer between these two worlds.

It can translate API requests into the appropriate telecom signaling transactions, manage transaction correlation, and return the result through the API interface.

The PAiCore Network API Gateway supports HTTP/REST, SS7/MAP, and Diameter interworking and uses an event-driven architecture to handle asynchronous telecom signaling workflows.

This architecture allows operators to expose network capabilities without requiring application developers to understand the underlying signaling protocols.

From Standardisation to Deployment

The Network API ecosystem is increasingly moving toward production deployment.

In March 2026, GSMA reported that 86 operator groups, representing more than 300 networks and 80% of global mobile connections, were aligned around a common API framework. GSMA also reported more than 60 channel partners commercialising Network APIs at scale.

As adoption expands, the focus increasingly shifts from:

“Can we define the API?”

to:

“Can we integrate it reliably with the network?”

That is where gateway infrastructure becomes critical.

The Production Architecture

Moving from a Network API specification to a production deployment requires more than defining the API contract.

A reliable implementation needs to account for:

  • API standardisation and interoperability
  • Authentication, security, and policy enforcement
  • API routing and transaction management
  • Protocol interworking
  • Asynchronous signaling and response correlation
  • Scalability and operational reliability
  • Integration with existing network functions

GSMA’s OPG.10 Open Gateway Technical Realisation Guidelines provide implementation guidance for stakeholders involved in deploying and using Open Gateway, including MNOs, service aggregators, and technology partners. The current guidance covers areas including API call routing, onboarding, consumption, operational processes, and consent-related flows.

Connecting Modern APIs to Existing Networks

The architectural direction is becoming clearer:

Standardised APIs Northbound → Policy & Security → Network API Gateway → Telecom Signaling → Existing Network Functions

This separation allows operators to modernise how network capabilities are consumed without requiring the underlying telecom infrastructure to be completely rebuilt.

For developers, it provides a simpler API-based interface.

For operators, it creates a practical path to expose existing network capabilities through modern, standardised services.

Explore PAiCore Network API Gateway

The PAiCore Network API Gateway is designed to bridge modern API applications with telecom signaling environments through multi-protocol interworking.

Explore the PAiCore Network API Gateway →
 
Developers, telecom engineers, and technology partners can also explore the open-source project:

Explore the PAiCore Network API Gateway on GitHub → 

References

From Specification to Production

A standardised Network API defines how applications interact with network capabilities.

Production infrastructure determines how reliably those requests reach the network and return the right result.

The objective is not to replace existing telecom systems.

It is to make those systems accessible through secure, scalable, and standardised programmable interfaces.

Read more at…

RELEASE NOTES

Network APIs for Fraud Prevention: Turning Mobile Network Signals into Digital Trust

Network APIs for Fraud Prevention: Turning Mobile Network Signals into Digital Trust

By PAiCore Technology ● 3 min read

Digital fraud is becoming increasingly sophisticated. Application-level authentication alone may not always provide enough context to determine whether a transaction or user should be trusted.

This is where Network APIs for fraud prevention are becoming increasingly relevant.

Mobile networks contain signals that can provide additional context about a subscriber and device. Standardised APIs can make selected network capabilities available to banks, fintech companies, retailers, and digital platforms.

How Can Network APIs Help Prevent Fraud?

Network APIs can provide additional signals that complement existing identity and fraud-prevention systems.

Examples include:

  • Number Verification — verifying whether a mobile number is associated with the device.
  • SIM Swap — identifying recent SIM changes that may indicate account-takeover risk.
  • Device Information — providing additional network-level context about a device.
  • Location Verification — checking whether a device is within an expected location.
  • Device Reachability — determining whether a device is connected and reachable.

These capabilities are increasingly represented through CAMARA Network APIs. The current CAMARA API portfolio includes mature APIs such as Number Verification, SIM Swap, Device Swap, Location Verification, and Device Reachability Status, alongside other authentication, fraud-prevention, location, and device-related capabilities.

The opportunity is particularly relevant to financial services, e-commerce, digital identity, and other applications where additional network signals can strengthen risk assessment.

Why Mobile Network Signals Matter

Traditional fraud-prevention systems often rely on application-level information such as passwords, OTPs, device data, and transaction behaviour.

Network APIs introduce another layer of context.

Signals originating from the mobile network can help applications make more informed decisions about whether a user, device, or transaction should be trusted.

This creates a new model:

Application Data + Network Signals → Better Risk Context

The GSMA’s 2026 Open Gateway update identifies fraud prevention as one of the strongest Network API use cases, highlighting deployments that help banks and retailers verify identities, detect SIM-swap fraud, and secure transactions in real time.

Where Does the Network API Gateway Fit?

A standardised API does not remove the underlying complexity of an operator network.

Network-level information may originate from infrastructure involving:

SS7/MAP | Diameter | HLR/AuC | HSS | AAA

A Network API Gateway provides the interworking layer between the application API and these telecom systems.

Conceptually:

Application → Network API → Gateway → Telecom Network → Network Signal

The gateway translates modern API requests into the appropriate telecom signalling interactions and returns the resulting information through the API layer.

PAiCore Network API Gateway

The PAiCore Network API Gateway bridges modern HTTP/API applications with carrier-grade telecom signalling through SS7/MAP and Diameter. Its event-driven architecture supports multi-protocol interworking and CAMARA-aligned Network API use cases, including Number Verification, Location Verification, Location Retrieval, and Geofencing Subscriptions.

This creates a practical bridge between:

Modern Digital Applications ↔ Network APIs ↔ Telecom Signalling

For fraud-prevention use cases, this architecture allows network-derived signals to become part of a broader digital trust and risk-assessment framework.

From Network Signals to Digital Trust

Network APIs are not designed to replace existing fraud-prevention systems. Instead, they can provide additional trusted context that helps applications make better-informed decisions.

Transaction Initiated
→ Application Requests Network Signals
→ Network API Gateway Connects to Telecom Infrastructure
→ Network Information Returned
→ Fraud/Risk Decision

This approach helps organisations move beyond relying on a single authentication signal toward a more contextual and informed approach to digital trust.

Even cleaner for the website:

Transaction → API Request → Network API Gateway → Network Signal → Risk Decision

I’d recommend the second version if the goal is to keep the article compact and eliminate excessive vertical spacing.

Explore PAiCore

The PAiCore Network API Gateway provides a foundation for exposing telecom network capabilities through standardised APIs and connecting modern applications with existing signalling infrastructure.

Explore the PAiCore Network API Gateway →

Developers, telecom engineers, and system integrators can also explore PAiCore’s open-source ecosystem:

Explore PAiCore on GitHub →

References

GSMA Open Gateway
https://www.gsma.com/solutions-and-impact/gsma-open-gateway/

GSMA Open Gateway — 2026 Market Update
 https://www.gsma.com/newsroom/article/from-ambition-to-execution-how-open-gateway-is-scaling-the-global-api-economy/

CAMARA API Overview
https://camaraproject.org/api-overview/

Building a New Layer of Digital Trust

Fraud prevention is becoming one of the most compelling applications of Network APIs.

Mobile networks already contain valuable signals. Network APIs provide a way to make those signals accessible to digital services.

The result is a new layer of context—helping applications move beyond traditional authentication toward network-enabled digital trust.

Read more at…

RELEASE NOTES

Network API Monetization: Turning Telecom Network Capabilities into Digital Services

Network API Monetization: Turning Telecom Network Capabilities into Digital Services

By PAiCore Technology ● 4 min read

Mobile operators have invested decades in building sophisticated network infrastructure. The next opportunity is to make more of those capabilities available as programmable Network APIs that developers and enterprises can consume.

This creates a potential new model for telecom:

Connectivity → Network APIs → Digital Services

How Can Operators Monetize Network APIs?

Network APIs allow operators to expose selected network capabilities through standardised interfaces.

Depending on the service, these capabilities can include:

  • Number Verification
  • SIM Swap
  • Location Services
  • Device Information
  • Quality on Demand

The GSMA Open Gateway initiative is helping establish a common framework for making these capabilities available to application providers, developers, and enterprises.

In March 2026, GSMA reported that 86 operator groups, representing more than 300 networks and 80% of global mobile connections, were aligned around a common Open Gateway API framework.

The scale of this ecosystem highlights the growing opportunity for operators to turn network capabilities into services that can be consumed beyond traditional telecom environments.

Monetization Requires More Than an API

Publishing a Network API is only one part of the equation.

For operators to turn network capabilities into scalable digital services, the API layer needs to connect reliably with the network infrastructure underneath.

A simplified architecture looks like this:

Developer / Application Layer
 ↓
 API & Policy Layer
 ↓
 Network API Gateway
 ↓
 SS7 / MAP / Diameter / Network Interfaces
 ↓
 Existing Network Assets

This is where the Network API Gateway becomes a critical architectural component.

The Infrastructure Behind Network API Monetization

A Network API Gateway provides the interworking layer between modern application environments and existing telecom infrastructure.

The PAiCore Network API Gateway supports multi-protocol interworking between HTTP/REST, SS7/MAP, and Diameter, allowing network capabilities to be exposed through modern API interfaces while retaining the underlying telecom infrastructure.

Its event-driven architecture is designed to support scalable telecom signalling workflows, while features such as high availability, load balancing, and fault tolerance help support carrier-grade deployments. PAiCore documents validated throughput of up to 9,000 transactions per second under sustained load testing.

This creates a bridge between:

Modern API Ecosystems ↔ Telecom Network Infrastructure

From Network Capability to Digital Service

The commercial opportunity for operators extends beyond simply exposing network data.

Network capabilities can become reusable digital services that application developers and enterprises can integrate into their own products and workflows.

For example:

Number Verification

Applications can use network-based verification to establish whether a mobile number is associated with a device.

SIM Swap

Network information can support fraud-prevention and identity-related use cases.

Location Services

Location-related network capabilities can enable applications to verify or retrieve information about a device’s location, subject to applicable network, privacy, and regulatory requirements.

Quality on Demand

Network APIs can provide applications with access to network quality capabilities for use cases that require specific connectivity characteristics.

CAMARA’s current API portfolio includes capabilities across authentication and fraud prevention, location services, device information, communication quality, and other network service categories.

The Role of PAiCore ECS-Lite

For use cases such as Number Verification and Silent Authentication, the API layer may also need to interact with service entitlement and authentication infrastructure.

PAiCore ECS-Lite can provide the entitlement layer associated with GSMA TS.43-based service entitlement architectures, helping support authentication-related Network API use cases.

This creates an architecture in which:

Application → Network API → Network API Gateway → Entitlement / Authentication Layer → Telecom Network

The result is an ecosystem where existing network capabilities can be exposed through modern interfaces while the underlying telecom infrastructure continues to perform its core functions.

Why Standardisation Matters for Monetization

For Network API monetization to scale, developers cannot be expected to build a completely different integration for every operator.

This is one of the reasons GSMA Open Gateway and CAMARA are important to the ecosystem.

GSMA Open Gateway provides the broader industry framework for standardised network API exposure, while CAMARA, an open-source project within the Linux Foundation, focuses on defining, developing, and testing telco northbound APIs.

Standardisation can help create a more consistent developer experience across operators and markets.

The commercial model therefore becomes:

Standardised APIs → Wider developer adoption → More use cases → Greater network utilisation → New digital service opportunities

From Connectivity Provider to Digital Service Platform

The opportunity for operators is not simply to create another API.

It is to transform existing network capabilities into reusable digital services that can be exposed, consumed, integrated, and potentially monetised across multiple application ecosystems.

The underlying network infrastructure remains valuable.

Network APIs provide a way to make that value more accessible.

And the Network API Gateway provides the bridge between the two.

Explore PAiCore Network API Gateway

The PAiCore Network API Gateway connects modern HTTP/API applications with telecom signalling through SS7/MAP and Diameter and supports CAMARA-aligned use cases including Number Verification, Location Retrieval, Location Verification, and Geofencing Subscriptions.
Explore the PAiCore Network API Gateway →

For developers, telecom engineers, and system integrators, the PAiCore open-source ecosystem provides an opportunity to explore the technologies behind modern telecom signalling and Network APIs.
Explore PAiCore’s open-source projects on GitHub →

References

GSMA Open Gateway
 Explore GSMA Open Gateway →

GSMA Open Gateway API Descriptions
 Explore the GSMA Open Gateway API portfolio →

CAMARA Project
Explore CAMARA →

CAMARA API Overview
 Explore the CAMARA API portfolio →

The Next Opportunity for Telecom

Network APIs are creating a new interface between mobile networks and the digital economy.

The opportunity is no longer limited to providing connectivity.

Operators can turn existing network capabilities into programmable services that developers and enterprises can consume through standardised APIs.

Connectivity built the network.
 Network APIs can help turn that network into a digital service platform.

Read more at…

RELEASE NOTES

Network API Interoperability: The Role of GSMA Open Gateway and CAMARA

Network API Interoperability: The Role of GSMA Open Gateway and CAMARA

By PAiCore Technology ● 4 min read

As mobile operators expose more network capabilities through Network APIs, interoperability is becoming one of the most important requirements for the telecom API ecosystem.

An application should not need a completely different integration for every operator.

This is the challenge that initiatives such as GSMA Open Gateway and CAMARA are designed to address.

What Is Network API Interoperability?

Network API interoperability means that developers and enterprises can consume network capabilities through consistent API interfaces, even when the underlying operator networks differ.

Without common standards, an application integrating with multiple operators could encounter different:

  • API interfaces
  • Authentication mechanisms
  • Integration processes
  • Network architectures

A standardised approach changes the model:

Application → Standardised Network API → Operator Network

GSMA Open Gateway provides an industry framework for exposing mobile network capabilities through common APIs, while CAMARA, hosted by the Linux Foundation, develops open API specifications behind many of these capabilities.

The GSMA Open Gateway ecosystem includes APIs covering use cases such as Number Verification, SIM Swap, device information, location services, and Quality on Demand.

Why Standards Do Not Solve Everything

Standardising the northbound API does not remove the complexity of the operator’s underlying network.

Different operators may continue to operate combinations of:

SS7/MAP | Diameter | HLR/AuC | HSS | AAA

This creates an important architectural requirement:

The standardised API layer must be able to interact reliably with existing telecom signalling environments.

This is where a Network API Gateway becomes important.

The Role of a Network API Gateway

A Network API Gateway acts as an interworking layer between modern API applications and telecom network infrastructure.

Conceptually:

Application → HTTP/REST → Network API Gateway → SS7/MAP / Diameter → Network

The gateway can translate API requests into the appropriate telecom signalling transactions and correlate responses back to the API layer.

The PAiCore Network API Gateway is designed for this role, providing multi-protocol interworking between HTTP/REST applications and telecom protocols including SS7/MAP and Diameter.

Its event-driven architecture and transaction correlation support asynchronous telecom signalling workflows.

The documented deployment has been validated at up to 9,000 transactions per second under sustained load testing.

From Standardised APIs to Interoperable Networks

GSMA’s OPG.10 Open Gateway Technical Realisation Guidelines provide implementation guidance for MNOs, service aggregators, and technology partners involved in deploying and using GSMA Open Gateway. The current 2026 guidance includes areas such as API call routing, onboarding, service consumption, consent, and operational integration.

The direction is therefore becoming clearer:

Standardise the API experience.

Preserve operator network flexibility.

Use interworking infrastructure to connect the two.

This separation is important:

Standardised APIs northbound.

Existing telecom signalling southbound.

A reliable gateway connecting the two.

For operators, this means existing network infrastructure can remain an important part of the architecture while modern applications gain access through standard API interfaces.

For developers, the benefit is abstraction: they can consume network capabilities without needing to understand every underlying telecom signalling protocol.

PAiCore Network API Gateway

The PAiCore Network API Gateway provides multi-protocol interworking between REST/HTTP, SS7/MAP, and Diameter and supports CAMARA-aligned Network API use cases including Location Retrieval, Location Verification, Geofencing Subscriptions, and Number Verification. It is designed around an event-driven architecture and supports carrier-grade deployment capabilities including high availability, load balancing, and fault tolerance.

Explore the Product

Learn more about the architecture, capabilities, Network API use cases, and deployment options:

Explore the PAiCore Network API Gateway →

The Network API Gateway is also part of PAiCore’s Signaling & Geolocation portfolio.

Explore the Open-Source Ecosystem

PAiCore’s Resources hub lists the Network API Gw Repository among its open-source projects, alongside other telecom signalling components.

Developers, telecom engineers, and system integrators can explore the PAiCore open-source ecosystem and follow the available projects through the PAiCore GitHub organisation:

Explore PAiCore on GitHub →

Note: The public GitHub organisation currently does not display public repositories, so the exact Network API Gateway repository URL should be added here once PAiCore provides/opens the specific repository.

Standards & References

GSMA Open Gateway

GSMA Open Gateway →
 
GSMA Open Gateway provides the broader industry framework for exposing mobile network capabilities through standardised APIs.

GSMA Open Gateway API Descriptions

GSMA Open Gateway API Descriptions →

The API portfolio provides descriptions of standardised Network API capabilities.

CAMARA Project

CAMARA Project→

CAMARA is the Linux Foundation open-source project focused on developing and testing standardised telco Network APIs.

GSMA OPG.10

GSMA OPG.10 – Open Gateway Technical Realisation Guidelines →

OPG.10 provides technical realisation guidance for stakeholders implementing and using GSMA Open Gateway.

Making Network APIs Work Across Real-World Networks

Network API interoperability is not simply about defining common APIs.

It is about creating the infrastructure that allows those APIs to work with the diverse telecom networks underneath.

Standardised APIs make network capabilities easier to consume.

Interworking infrastructure makes those APIs practical across real-world telecom environments.

And the Network API Gateway provides the bridge between the two.

The future of Network APIs depends not only on standardisation—but on how effectively those standards connect with the networks already in place.

Read more at…

RELEASE NOTES

Number Verification Without SMS OTP: How Network APIs Enable Silent Authentication

Number Verification Without SMS OTP: How Network APIs Enable Silent Authentication

By PAiCore Technology ● 4 min read

Can a mobile number be verified without sending an SMS OTP?

Yes. And Network APIs are making it possible.

Traditionally, digital services verify a mobile number by sending an SMS one-time password (OTP). While widely used, this approach introduces additional user interaction and can create opportunities for phishing and social-engineering attacks.

Network APIs and SIM-based authentication are enabling a different approach—using trusted signals from the mobile network to verify a user’s mobile number.

The GSMA Open Gateway Number Verification API, developed within the CAMARA ecosystem, enables applications to verify or retrieve the mobile phone number associated with a device.

It can support silent authentication, allowing verification to take place without requiring the user to manually enter an SMS OTP.

How Does Number Verification Work?

The application interacts with a standardised API, while the underlying authentication process can use network-based or SIM-based mechanisms.

At a high level, the architecture can be represented as:

Application → Network API → Gateway → Telecom Network / Authentication Infrastructure

From the application’s perspective, the process can remain simple.

Behind the API, however, multiple network and authentication components may work together to establish and verify the subscriber’s identity.

This is where a Network API Gateway becomes an important architectural component.

The Role of the Network API Gateway

The PAiCore Network API Gateway provides an interworking layer between modern API applications and telecom signalling environments, including SS7/MAP and Diameter.

This allows network capabilities to be exposed through modern APIs without requiring application developers to implement telecom-specific signalling protocols.

The gateway effectively bridges two different worlds:

Modern API Applications
↓
HTTP / REST
↓
Network API Gateway
↓
SS7 / MAP / Diameter
↓
Telecom Network

This abstraction allows developers to consume network capabilities through familiar API interfaces while operators can continue leveraging their existing telecom infrastructure.

Explore the PAiCore Network API Gateway

The PAiCore Network API Gateway supports multi-protocol interworking between REST/HTTP, SS7/MAP, and Diameter, along with CAMARA-aligned Network API use cases such as Number Verification.

Explore the PAiCore Network API Gateway →

SIM-Based Authentication and the Entitlement Layer

Number Verification can also involve SIM-based authentication mechanisms.

Depending on the implementation and network architecture, the authentication ecosystem can include an Entitlement Server based on GSMA TS.43, which defines a framework for service entitlement configuration.

GSMA ASAC specifications further extend the authentication model for scenarios including Wi-Fi connectivity.

This introduces another important architectural layer:

Application → Network API → Network API Gateway → Authentication / Entitlement Infrastructure → Mobile Network

For operators implementing these capabilities, the ability to integrate the API layer with the underlying entitlement and authentication infrastructure becomes essential.

PAiCore ECSaaS

PAiCore ECSaaS provides an entitlement capability that can be integrated with Network API architectures to support standardised authentication and Number Verification experiences.

Combined with the PAiCore Network API Gateway, this architecture can help connect modern application interfaces with the underlying telecom and authentication infrastructure required to deliver network-based verification.

The result is a more seamless authentication experience while allowing operators to make better use of capabilities already available within their networks.

Why Silent Authentication Matters

Moving beyond SMS OTP can provide several advantages for digital services and users.

Reduced User Friction

Users don’t necessarily need to wait for an SMS, retrieve a code, and manually enter it into an application.

Stronger Network-Based Trust

Verification can leverage information and authentication mechanisms associated with the mobile network and SIM.

Improved User Experience

A more seamless verification flow can reduce interruptions during account registration, login, or other authentication journeys.

New Network API Use Cases

Number Verification is part of a broader movement toward using trusted mobile-network capabilities for identity, security, fraud prevention, and other digital services.

The Mobile Network as an Identity Platform

For decades, mobile networks have primarily been viewed as connectivity infrastructure.

Network APIs are changing that perspective.

Capabilities traditionally embedded within telecom infrastructure can increasingly be exposed through standardised APIs and consumed by applications, enterprises, and digital platforms.

Number Verification is one example of this shift.

The mobile network is becoming an identity platform—not just a connectivity platform.

As GSMA Open Gateway and CAMARA continue to standardise Network API capabilities, the opportunity for operators is to transform existing network intelligence into services that developers can consume through modern APIs.

Explore and Test the Open-Source Project

The evolution of Network APIs depends not only on standards, but also on open technologies that developers and telecom engineers can explore, test, and build upon.

The PAiCore Network API Gateway is available as an open-source project, providing developers, system integrators, and telecom engineers with an opportunity to explore the technology behind modern telecom signalling and Network API architectures.

Explore the Project on GitHub

Explore & Test the PAiCore Network API Gateway on GitHub →

We welcome developers, telecom engineers, system integrators, and the wider open-source community to explore the project, test the implementation, share feedback, and contribute to its continued development.

Standards & Industry References

The development of Number Verification and SIM-based authentication is supported by several industry standards and initiatives:

The Future of Mobile Identity

SMS OTP has played an important role in digital authentication, but the evolution of Network APIs is opening new possibilities.

By combining standardised APIs, network-based authentication, SIM capabilities, and telecom infrastructure, operators can provide applications with trusted network intelligence through simpler interfaces.

The architecture may be complex underneath.

But the experience for the user doesn’t have to be.

The future of mobile identity could be silent, network-based, and API-driven.

Explore the Network API Gateway. Test the open-source project. And help shape the next generation of programmable telecom networks.

Read more at…

RELEASE NOTES

Network API Gateway: Bridging Modern APIs and Telecom Signaling

Network API Gateway: Bridging Modern APIs and Telecom Signaling

By PAiCore Technology ● 3 min read

Network APIs are making it possible for applications to access capabilities traditionally embedded inside mobile operator networks.

Use cases such as Number Verification, Location Verification, fraud prevention, and Quality on Demand can increasingly be exposed through standardised APIs.

But while the API presented to a developer may be simple, the network infrastructure behind it often isn’t.

A modern Network API may ultimately need to interact with telecom technologies such as SS7, MAP, SIGTRAN, Diameter, HLR/AuC, HSS, or 3GPP AAA.

Connecting these environments reliably is one of the key architectural challenges in implementing Network APIs.

The Role of a Network API Gateway

A Network API Gateway provides the translation and orchestration layer between modern application interfaces and telecom signaling infrastructure.

Conceptually, the architecture looks like:

Application → HTTP/REST → Network API Gateway → SS7/MAP or Diameter → Mobile Network

This approach allows application developers to consume network capabilities through familiar API interfaces without requiring them to implement telecom-specific signaling stacks.

It also aligns with the industry’s move toward standardised Network APIs.

GSMA Open Gateway provides a framework for exposing operator network capabilities through common APIs, while CAMARA develops standardised API specifications designed to simplify application-to-network integration.

Why Multi-Protocol Interworking Matters

Operators do not necessarily have a single underlying network architecture.

Existing deployments can include SS7/MAP and Diameter-based environments, depending on the network function, technology generation, and deployment architecture.

A Network API Gateway therefore needs to provide more than HTTP exposure.

It must reliably translate API requests into the appropriate signaling transactions and correlate the resulting responses.

The PAiCore Network API Gateway is designed for this role, bridging modern HTTP/API applications with telecom protocols including SS7/MAP and Diameter.

Its event-driven architecture supports asynchronous processing and transaction correlation, helping decouple API requests from the response characteristics of telecom signaling.

The documented implementation has been validated at throughput of up to 9,000 transactions per second under sustained load testing.

Standards-Led Network API Architecture

The broader Network API ecosystem is increasingly being standardised.

GSMA Open Gateway establishes a common industry framework for exposing mobile network capabilities, while CAMARA, hosted by the Linux Foundation, develops open Network API specifications and implementations.

This creates an important architectural separation:

Standardised APIs northbound.

Existing telecom signaling southbound.

A reliable gateway connecting the two.

For operators, this means existing network infrastructure can remain an important part of the architecture while modern applications gain access through standard API interfaces.

For developers, the benefit is abstraction: they can consume network capabilities without needing to understand every underlying telecom signaling protocol.

PAiCore Network API Gateway

The PAiCore Network API Gateway is an open-source telecom signaling component designed to bridge modern API-based applications with carrier-grade telecom signaling environments.

It supports multi-protocol interworking and provides a foundation for functions such as STP, Diameter Routing Agent (DRA), and multi-protocol proxying, while also supporting CAMARA-aligned Network API use cases.

Explore the PAiCore Network API Gateway product page →

The product page provides further information about the gateway’s architecture, capabilities, supported Network API use cases, and deployment considerations.

For developers and telecom engineers interested in PAiCore’s open-source ecosystem:

Explore PAiCore on GitHub →

The Objective Is Straightforward

Make modern APIs the front door to telecom capabilities—without forcing the network underneath to be rebuilt.

As Network APIs continue to evolve, the ability to connect standardised application interfaces with existing telecom signaling infrastructure will become increasingly important.

A Network API Gateway provides that bridge—helping operators modernise access to network capabilities while continuing to leverage the infrastructure already in place.

Read more at…

RELEASE NOTES

The Rise of Network APIs: Why Telecom Networks Are Becoming Programmable

The Rise of Network APIs: Why Telecom Networks Are Becoming Programmable

By PAiCore Technology ● 4 min read

Telecom networks have always contained valuable capabilities—from subscriber identity and authentication to location, connectivity, and quality of service.

Historically, however, accessing these capabilities required specialised telecom integrations and knowledge of protocols such as SS7, MAP, and Diameter.

Network APIs are changing that model.

Network APIs provide a modern interface through which applications, enterprises, and digital platforms can access selected capabilities of mobile networks. Instead of requiring every application developer to understand telecom signalling, network capabilities can increasingly be exposed through standardised APIs.

The industry is building a common ecosystem around GSMA Open Gateway and CAMARA, with operators, technology providers, aggregators, and developers working toward more interoperable Network APIs. GSMA describes Network APIs as a way to make mobile-network capabilities accessible through standardised interfaces, including capabilities related to identity, location, and quality of service.

From Connectivity to Programmable Network Services

The significance of Network APIs goes beyond simply providing another interface.

Traditionally, mobile networks were largely consumed through telecom-specific systems. Applications often depended on intermediaries, proprietary interfaces, or complex integrations to access network capabilities.

The Network API model introduces another layer:

Application → API → Network Capability

This allows capabilities already available within an operator’s infrastructure to become services that applications can consume through modern interfaces.

Examples include:

  • Number Verification
  • SIM Swap detection
  • Location Verification
  • Location Retrieval
  • Geofencing
  • Quality on Demand
  • Device information
  • Silent Authentication

The GSMA Open Gateway API portfolio includes capabilities across areas such as authentication and fraud prevention, location services, device information, connectivity, and communication quality. Many of the service APIs are defined within the CAMARA project.

Why Standardisation Matters

One of the biggest challenges for Network APIs is interoperability.

If every operator exposes a network capability differently, an enterprise wanting to deploy across multiple markets still faces multiple integrations.

This is where GSMA Open Gateway and CAMARA become important.

CAMARA is an open-source project within the Linux Foundation focused on defining, developing, and testing standardised APIs for accessing telecom network capabilities. It works closely with the GSMA Operator Platform Group to align API requirements and definitions.

GSMA Open Gateway provides the broader industry framework for making these standardised network capabilities available through mobile operators.

The objective is straightforward:

Standardise the API experience while allowing operators to retain their underlying network infrastructure.

This approach is already moving beyond experimentation. In March 2026, GSMA reported that 86 operator groups representing more than 300 networks and 80% of global mobile connections were aligned around a common API framework, with more than 60 channel partners involved in commercialising Network APIs.

The Network API Gateway: Connecting APIs to Telecom Signalling

Standardised APIs solve the northbound application-interface challenge. They do not, by themselves, remove the complexity of the network underneath.

An operator may still have infrastructure based on technologies such as SS7/MAP, SIGTRAN, and Diameter, together with HLR/AuC and 3GPP AAA environments.

This is where a Network API Gateway becomes an important architectural component.

PAiCore’s Network API Gateway is designed to bridge modern HTTP/API applications with carrier-grade telecom signalling through SS7/MAP and Diameter. Its event-driven architecture provides protocol interworking while helping decouple API requests from the response characteristics of telecom signalling.

The architecture can therefore be represented as:

Modern Applications
 ↓
 REST / HTTP APIs
 ↓
 Network API Gateway
 ↓
 SS7 / MAP or Diameter
 ↓
 Mobile Network

This approach allows operators and technology providers to modernise access to existing network capabilities without requiring every application to implement telecom signalling protocols.

PAiCore’s current Network API Gateway also supports CAMARA-aligned use cases, including capabilities such as Location Retrieval, Location Verification, Geofencing Subscriptions, and Number Verification.

Where Network APIs Are Heading

The Network API ecosystem is moving from standardisation and experimentation toward broader commercial adoption.

GSMA’s 2026 materials describe Network APIs as an increasingly important interface for exposing mobile-network capabilities to enterprises and applications, with the industry now focused on scaling adoption, commercialisation, and interoperability.

For operators, the opportunity is to turn existing network capabilities into programmable services.

For enterprises, Network APIs can provide new sources of trusted network intelligence.

For developers, they offer a simpler way to consume telecom capabilities without requiring deep knowledge of underlying signalling technologies.

And for infrastructure providers, the challenge is to connect the standardised API world with the complex signalling environment that already exists.

That is the role of the Network API Gateway: making the network programmable without requiring the network to be rebuilt.

Explore PAiCore Network API Gateway

PAiCore’s Network API Gateway provides multi-protocol interworking between REST/HTTP, SS7/MAP, and Diameter and supports CAMARA-aligned Network API use cases. The platform is designed around an event-driven architecture and supports carrier-grade deployment requirements such as high availability, load balancing, and fault tolerance.

Explore PAiCore Network API Gateway

PAiCore also provides open-source repositories for developers, system integrators, and telecom engineers exploring modern telecom signalling architectures.

Explore PAiCore Open-Source Repositories

Standards & Industry References

GSMA Open Gateway

GSMA Open Gateway

GSMA Open Gateway provides the industry framework for standardised access to mobile-network capabilities.

CAMARA

CAMARA Project

CAMARA is the Linux Foundation open-source project developing and testing standardised telco Network APIs.

GSMA Open Gateway API Descriptions

GSMA Open Gateway API Descriptions

The GSMA maintains descriptions of mature Open Gateway APIs, with the northbound service APIs defined within the CAMARA project.

GSMA Open Gateway Technical Realisation Guidelines

GSMA Open Gateway Technical Realisation Guidelines

These guidelines cover areas including API routing, consent, onboarding, service consumption, and operational integration.

The Future of Programmable Telecom Networks

Network APIs are becoming a new interface to the mobile network.

The opportunity is not simply to expose telecom capabilities through APIs, but to make those capabilities easier to consume, more interoperable, and more accessible to the wider digital ecosystem.

As standardisation through GSMA Open Gateway and CAMARA continues to mature, the next phase of telecom innovation will depend on how effectively the industry connects modern applications with the network capabilities already in place.

The network doesn’t need to be rebuilt to become programmable. It needs the right interface to unlock what is already there.

Read more at…

RELEASE NOTES

Building Operationally Efficient SMS Platforms: Why Small Improvements Matter

Building Operationally Efficient SMS Platforms: Why Small Improvements Matter

By PAiCore Technology ● 3 min read

Building a reliable SMS platform isn’t just about delivering messages. As messaging volumes grow, operators need platforms that are easy to manage, produce accurate operational data, and continue performing reliably under sustained load.

While new features often receive the most attention, day-to-day operational improvements can have the greatest long-term impact. Streamlined administration, efficient resource management, and accurate reporting all contribute to lower operational overhead and a better experience for operations teams.

At PAiCore Technology, we believe continuous improvement is essential to building resilient telecom infrastructure. That’s why Open Source SMSC v3.2.0 includes several enhancements focused on platform administration, reporting accuracy, and runtime performance.

Simplifying Platform Administration

Managing messaging infrastructure should be intuitive, especially as deployments grow.

Open Source SMSC v3.2.0 introduces dedicated management pages for SMPP Gateway and HTTP Gateway configuration, replacing modal-based administration with a more structured interface.

This approach makes gateway configuration easier to navigate, simplifies day-to-day administration, and provides a more consistent experience for operations teams responsible for managing multiple messaging connections.

Improving Reporting Accuracy

Operational reporting is critical for monitoring platform performance, troubleshooting issues, and supporting business processes.

Multipart SMS messages present a particular challenge because a single logical message is transmitted as multiple segments. If reporting generates records for segments that are never sent, operational data becomes unnecessarily complex and can make analysis more difficult.

Version 3.2.0 improves multipart SMS Call Detail Record (CDR) generation by preventing unnecessary records for unsent message segments.

The result is cleaner reporting and operational data that more accurately reflects actual messaging activity.

Optimising Runtime Performance

As messaging platforms process increasing traffic volumes, efficient resource management becomes just as important as message throughput.

Earlier implementations of pending Delivery Receipt (DLR) storage could accumulate stale entries over time, increasing memory usage and requiring additional operational attention.

Open Source SMSC v3.2.0 addresses this by introducing an optimised Caffeine Cache for pending DLR management.

Entries automatically expire after a configurable period, while cache size limits help prevent unbounded growth.

This approach helps:

  • Reduce memory consumption
  • Improve runtime stability
  • Prevent the accumulation of obsolete data
  • Support more efficient long-running operations

Continuous Improvement for Modern Messaging Platforms

Operational excellence is rarely achieved through a single feature.

It is the result of many incremental improvements that simplify administration, strengthen reporting, and improve platform stability over time.

The enhancements introduced in Open Source SMSC v3.2.0 reflect this philosophy by helping operators spend less time managing infrastructure and more time delivering reliable messaging services.

Together with new capabilities such as HTTP Authentication, SMPP over TLS, multi-session multipart SMS processing, and SMPP ↔ HTTP Proxy Mode, these improvements contribute to a more maintainable, scalable, and resilient messaging platform.

Learn More

Operational improvements are an important part of Open Source SMSC v3.2.0, reflecting PAiCore Technology’s ongoing commitment to building open-source telecom solutions that solve real operational challenges.

To learn more:

Join the Community

Open-source innovation is driven by collaboration.

We welcome feedback, feature requests, and contributions from operators, developers, system integrators, and the wider telecom community as we continue advancing open-source, scalable, and reliable telecom messaging technology.

Read more at…

RELEASE NOTES