Last Modified October 1, 2026
  1. Home
  2. Guides
  3. Activation API V1
  4. Activate the Device - Custom

Activation API V1 Custom Activation

Activate the License

  1. Step 1 : Query the License Status
  2. Step 2 : Capture additional information for Activation / Re-Activation

To activate the License and device, the App needs to perform the following:

  • capture the License Activation Code

  • perform a WEB_Query to determine status of the License and what additional information to capture from the User

  • capture additional License information from the User

  • perform a WEB_Activate or WEB_Reactivate

 

Step 1 : Query the License Status

Capture the License Activation Code from the User, and perform the WEB_Query call.

The App should watch for the following key results:

errNo = 8 (ERR_ACTIVATION_EXPECTED)

This is the initial activation of the following license types:

  • a Single-User / Multi-Computer license with the "Roll-Over Re-Activation
errNo = 9 (ERR_REACTIVATION_EXPECTED)

This is the activation of an additional device / browser or re-activation of a device / browser for the following license types:

  • a Single-User / Multi-Computer license with the "Roll-Over Re-Activation
errNo = 19 (ERR_ACTIVATION_EXPECTED_MU)

This is the initial activation of the following license types:

  • a Single-User / Multi-Computer license without the "Roll-Over Re-Activation
  • Multi-User License
  • Floating License
errNo = 20 (ERR_REACTIVATION_EXPECTED_MU)

This is the activation of an additional device / seat or re-activation of a device / seat for the following license types:

  • a Single-User / Multi-Computer license without the "Roll-Over Re-Activation
  • Multi-User License
  • Floating License

 

Step 2 : Capture additional information for Activation / Re-Activation

Based on the options enabled for your DNA Product and the status of the License determined using the WEB_Query API call, proceed to capture additional information from the User and do an Activation or Re-activation.

The additional information that you need to capture from the User will depend on the License type / options and if this is an initial activation or seat activation, or re-activation as follows:

License Type Options Capture this additional information
Single-User
  • Roll-over Re-activation
  • User Authentication

On Activation:

  • License password (max 16 chars)
  • Email (optional)

On Re-activation:

  • Current License Password
  • New and Never Used Password
Single-User
  • No Roll-Over Re-activation
  • User Authentication

On Activation:

  • License password (max 16 chars)
  • Email (optional)

On Re-activation:

  • Current License Password
Single-User
  • No Roll-Over Re-activation
  • No User Authentication

On Activation:

  • Email (optional)

On Re-activation:

  • No info required
Multi-User
Floating
  • No Roll-Over Re-activation
  • User Authentication

On 1st seat Activation:

  • License password (max 16 chars)
  • Email (optional)

On other seat activation or Re-activation:

  • Current License Password

The Email is optional but recommended. A password can be recoved using the WEB_ResetPassword API call from the application, or from the DNA Control Panel, or from the License Manager Portal.

If your product does not use "User Authentication", then you will need to define (hard-code) a "global" default password in your application to be used by all Licenses and used in all API calls.
See User Authentication     for information on using or not using User Authentication.

 

With the above information, and based on the status of the License Code:

The WEB_Activate and WEB_Reactivation will respond with a new DNA License to be saved.

The App should watch for the following key results:

dnaError   <=   0
 
  • The License and device has been activated or re-activated and is currently valid
  • The Application can run
  • for ERR_ACTIVATIONS_EXCEEDED(-3), (possible when using Roll-Over Re-activation   ) the App can display a warning message to the User
dnaError   >   0
 

  • For most failure error codes, we recommend displaying a generic message in order to avoid providing too much information to illegitimate user, such as :

    Please verify your License Code and Password

  • The Application should not be allowed to run, or could be allowed to run with limited functionality (ex: a "Demo" mode)
  • For some failure error codes, the License information provided by the User was correct, and a more descriptive error message is recommended as follows:
ERR_BANNED_ACTIVATION_CODE (10)
  • The License is disabled / banned
ERR_CODE_HAS_EXPIRED (16)
  • The License has expired
ERR_ACTIVATIONS_EXCEEDED_MU (21)
  • The maximum Devices or Seats for this License has been exceeded
  • Display an appropriate error message about de-activating another device / browser

See DNA API Error Codes     for the definition of the different Error Codes.