On this page

This tutorial guides you through the steps of developing your web server code to communicate with Samsung’s E-FOTA Server to:

  • Register enterprises for the E-FOTA service.
  • Get Android firmware information for various Samsung device models.
  • Schedule firmware updates for specified groups of devices.

This section provides an introduction to the tutorial.

Differences between E-FOTA v1 and E-FOTA v2

See what's new for an overview on what changes are in E-FOTA v2. For more information, go to the SEAP Samsung Enterprise FOTA page.

Using E-FOTA v1 with E-FOTA v2

While E-FOTA v2 brings new features with 5 new additional APIs, developers are still able to use E-FOTA v1 APIs while using E-FOTA v2.

For example, use groupRegister from E-FOTA v2 to register a group of devices then push a group update using serverInit from E-FOTA v1.

NOTE — To prevent errors, verify that the POST HTTP URL matches the E-FOTA version for the API.
 For example:
  • groupRegister URLPOST
  • serverInit URLPOST

Name space differences

In E-FOTA v2, there are 4 updated APIs, 3 of the APIs have the following name changes:

E-FOTA v1 API E-FOTA v2 API revision Description
firmware firmwareList

API to return the list of firmware versions available.

licenseInfo licenseInfo

API to return information about E-FOTA license.

serverInit forceUpdate

API to push a force update to a list of E-FOTA devices.

Elements in the request parameter have also changed for the 4 updated APIs in E-FOTA v2. For more details about these changes see the E-FOTA REST API reference.


If you haven't done so, review the following sections before you begin this tutorial:

  1. Before you begin
  2. Set up your web server

After completing the steps from the sections above, you'd have the following requirements to continue with the tutorial:

  1. Web server — If you haven't set up your web server, read about how to set up your web server before starting.
  2. E-FOTA license key — The E-FOTA REST API license key is used to authenticate yourself to the E-FOTA server when sending an API call to request an OAuth 2.0 access token. Check that you've followed the steps to request a REST API key before proceeding.
    • client_id — Used to generate an OAuth 2.0 access token to authenticate your identity in REST API calls. A hyphen-separated 32-character hexadecimal string, for example,aaaa1111-bb22-cc33-dd44-eeeeee555555.
    • client_secret — Used to generate an OAuth 2.0 access token to authenticate your identity in REST API calls. A hyphen-separated 32-character hexadecimal string, for example,bbbb2222-cc33-dd44-ee55-ffffff666666.

Tutorial Progress

You've completed 1/6 steps! Go to the next step.