Native API Reference

Tizen Native API is carefully selected and tightly managed APIs from the Tizen Native subsystems. The Native API is divided into dozens of API modules; each module represents a logically similar set of submodule APIs, which can be grouped into the same category.

The previous versions of Tizen Native APIs supports mobile, wearable, and IoT devices seperatly. They contain somewhat different modules.

For more information, see API Reference for Mobile, Wearable, Iot-Headed, or Iot-Headless.

Since 8.0, Tizen supports a single set of Native APIs. For more information, see API Reference for 8.0.

Required Header

To be able to use an API, you need to include a header in which API is defined. You can find required headers in API reference as illustrated below:

Figure: Required Header

Required Header

Some of the Tizen Native APIs require features to prevent your application from being shown in the application list on the official site for Tizen applications. If related Feature is included in API reference as shown below and your application uses that feature, then you need to declare the feature in the tizen-manifest.xml file. For more information, see Application Filtering.

Figure: Related Feature

Related Feature

Structure of Function Descriptions

In the function documentation for each module, the functions are described using a unified structure, illustrated in the below example.

Figure: Reference Structure

Reference Structure


The privilege is essential part to get access grant for privacy related data or sensitive system resources. For more information, see Privileges. Some of Tizen Native API functions require adding appropriate privileges (defined in each API’s Privilege section in the specification) to the tizen-manifest.xml file. If required privileges are not included in the tizen-manifest.xml file, then the function will return TIZEN_ERROR_PERMISSION_DENIED error.

For example, see the “Privilege:” section in the following picture:

Figure: Privilege