Last Modified October 1, 2026
  1. Home
  2. Guides
  3. Activation API V1
  4. Introduction

Activation API V1 - Overview

  1. Introduction
  2. SAAS or Device Application
  3. Activation API Helper Functions

 

With the Activation API method you can implement a licensing model and enforce access to your Application across all platforms, and independant of how your Application is implemented on any given device, i.e. as an Executable on the device or as a web-based SAAS Application accessed using the device browser.

You can combine the Activation API implementation on any device (including mobile devices) with our DNA Library based implementation for Windows, MAC, LINUX and ANDROID devices.

The Activation API method uses HTTPS POST / GET commands with JSON encoded parameters to implement the software_DNA licensing solution and requires no DNA Library to be installed on the User’s device.

The Activation API licensing solution would typically be used for the following:

  • a web-based SAAS application, to enforce licensing on a web-based Login and manage the number of browser sessions
  • an executable-based Device application used on desktops, laptops, tablets, mobile devices
  • a cross-platform executable-based Device application used on desktop, laptops, tablets, mobile devices
  • a combination of the above
  • enforcing access to a web-based SAAS application only when associated with a valid desktop/laptop license

The Activation API method can be implemented for the following license types:

  • Single-User / Multi-Computer Licenses without the "Roll-Over Re-Activation" option and with or without the "User Authentication" option.
  • Multi-User Licenses
  • Floating Licenses

A given License Activation Code can be used on any device within the licensing parameters of your DNA Product configuration.

 

SAAS or Device Application

How you implement the Activation API method will depend on the application type:

SAAS Application

The Application is accessed using a device browser and typically includes a Login and/or Account Activation page to gain access to the SAAS App.

The Application itself resides on your web-server.

The DNA License is stored as a signed Browser Cookie on the device browswer.

Each browser is seen as a different device (ex: using Chrome and Edge on the same device to access the App).
Device Application

The Application is an executable on the Device and would require the activation of a License before it can be used.

The DNA License is stored as a file on the device.

The License can be node-locked to the device.

Each step of the Activation API process is explained and discussed in the following sections.

If you would like to experience the software_DNA solution immediately, you can download examples of simple working applications, from your DNA Control Panel account (under the Resources -> Code Samples menu), including:

  • Hello World Web SAAS - source code - Annotated source code demonstrating key process flow and API calls for an implementation of a web-based application that you can upload to your web-server to try.
  • HelloWorld Web Windows - source code - Annotated source code to demonstrate using the Activation API from a Windows executable. Full project that can be compiled.
  • HelloWorld Web Android - source code - Annotated source code to demonstrate using the Activation API from an Android application. Full project that can be compiled.

For Web SAAS Activation, see our live demo here:

SAAS Activation Demo 

You can get a License Code for our HelloWorld P0002964 demo product on our Resources -> Code Samples page.

 

Activation API Helper Functions

When using the Activation API process, several key functions are needed in the App to complete the sofware_DNA implementation, including:

  • sending HTTPS POST / GET Requests and receive Responses using JSON-based strings
  • using HMAC256 Hashing to create and verify the SIGNATURE field in the Requests and Responses
  • read/write the DNA License on the device as a Browser Cookie (SAAS App) or a file (Device App)
  • optionaly, implementing a local validation function for a faster validation and to limit the number of DNA Server Validations

For selected coding environments, we provide "As Is" a set of Helper API Functions to simplify the implementation.
See Helper Functions     for details.

The Helper Functions are provided in source code and you can use / modify as required for your implementation, or choose to directly issue HTTPS requests as per the Activation API V1 Reference documentation.