Introduction to the Ignite Services API

The Ignite Services API exposes some of Ignite's functionality to the third-party trusted applications via Android Interface Definition Language (AIDL). Ignite acts as a server providing abilities to retrieve applications, install or "get" application info, and update applications. Applications using the Ignite Service API are treated as "client".

The following diagram outlines the main components for interacting with DT Ignite


1. Ignite

DT Ignite is a Dynamic Preload Platform (DPP), i.e., an Android application which allows Mobile Network Operators (MNOs) to assist in the application preinstall process. Ignite is preloaded on Android devices, and provides MNOs with the ability to control the installed applications on Android by delivering them over-the-air vs. preloading them via firmware. All applications downloaded via Ignite can be removed/uninstalled by the end-user.

2. Ignite Services API

The Ignite Services API is a feature of Ignite that permits authenticated MNO partner applications to securely perform interactions with applications and application metadata. Example services include retrieving application metadata and installing and/or updating of Android applications. The Ignite Services API provides a method for suggesting, downloading, installing apps as well as reporting on app installation status. The underlying communication with Ignite Services API takes place using AIDL. To simplify integration with the API, integrations directly with AIDL should be avoided. Instead, integrations should be managed via the Ignite Services Client SDK, a software library provided by DT that wraps the AIDL interactions and provides a simple method for inclusion into integrator applications.

3. Ignite Services Client SDK

The Ignite Services Client SDK is a software library which provides a set of features to consume the Ignite Services API AIDL in a convenient and simple way. Ignite Services Client SDK manages authentication and authorization, and it provides simple methods to consume all parts of the Ignite Services API. It is recommended that all integrator applications use only the Ignite Services Client SDK to consume Ignite Services APIs.

Back to Top ⇧