Working Group Two is a mobile core network built the cloud way, with APIs that let you enhance or build products on top of modern APIs that gives access to the subscriber's telco data.
How it works
The API platform lets you access individual subscriber's calling, SMS/MMS, data, roaming, and more, using OAuth 2.0 to grant consent, built on top of modern gRPC APIs.
By visiting Developer portalopen in new window you may create your product and corresponding OAuth 2.0 clients. You will also add additional information such as contact details and product description.
Our APIs are built with gRPC
At WG2 we had to build a high-performance, scalable, and efficient client-server architecture, and after exploring various options we landed on gRPC. One of the reasons we chose gRPC is its use of a binary protocol for communication between the client and server, which results in improved performance compared to a text based alternative like, for example, REST.
Another key benefit of gRPC is its simple service definition, which is defined using the Protocol Buffers language. This makes it easy to define and maintain the contract between the client and server, allowing us to quickly and easily develop and deploy our APIs and services.
We also appreciate that with gRPC you can generate client libraries for multiple programming languages based on the service definition. This makes it easier for our teams and partners to consume our APIs in their preferred languages, saving everyone time and effort. Currently C++, Java, Python, Go, Rust, C# / .NET, Kotlin, Node and more are supported. A full list of currently supported languages is available under "Supported languages"open in new window on the gRPC documentation page.
Overall, we are using gRPC because of its great performance, simple service definition, cross-language support, and type-safety. We believe that these benefits will help us deliver high quality APIs with a great developer experience to our partners.