Last modified: 05-apr-2017


A warm welcome to the T-Mobile Customer Api documentation website.

The T-Mobile Customer Api - or short capi - is a customer centric Api that is created by T-Mobile to facilitate both T-Mobile and external third parties in creating new and exciting applications to support our customers.
Our motivation for creating this Api is the ever increasing need for information and functionality any time, any place and anywhere. At the same time, this should not come at the expense of a secure, stable and trusted customer experience. This Api has been constructed to facilitate other parties in integrating T-Mobile customer related information and functionality into their environments, while respecting these requirements.

Customer Centric

The T-Mobile Customer Api is customer centric in two important ways. Firstly, all data and functionality is customer bound. Within the context of a customer you can find his or her bundlestatus, his or her subscription data, etc.. There might be generic anonymous services but no functionality related to sets of multiple customers or beyond the context of a single authenticated customer is offered. Secondly, a customer must give explicit approval for an application to use his or her data by the usage of tokens. These tokens are managed from within the My T-Mobile environment.

Status and Future

At this point in time, the Customer Api is no longer in beta status, but is considered live for production. This means that it is used by T-Mobiles' own applications and can be used by partners. The Api has expanded with additional facilities (the oAuth implementation) to allow for a standardized integration and fluent customer experience.
With regards to functionality, we expect to expand the Api into several areas. At this point in time the functionality is limited, but be sure to watch out for news in this area. The Change Log is an additional source of information on the latest status.


The Customer Api is a RESTful Api that should enable developers to write and test applications with simple tools, using familiar skills and relatively low costs and time. You can use almost any client and programming language to access the Api, as long as you abide by the rules of the Http specification (1.1).
Nonetheless the Api is still complicated by the business domain at hand (the turbulent mobile communication industry) and the fact that RESTful Apis are not standardized but driven by common architectural concepts.
We have tried to overcome the first issue by providing you with detailed descriptions on the resources we have enabled through this Api. The second issue is covered by providing you with details on our implementation of the REST architectural style, plus giving you access to a number of examples and utilities.

Getting Started

We recommend you to read through the REST related sections, the possible error codes and the explicit descriptions of the resources you want to use. But for those of you eager to start coding, follow the following steps: