API Implementation

Home > Encryption > API Implementation

Encryption via API's

Using our API gives software developers the ability to access functions directly from within their software. These functions would normally concern the following three scenarios:

  • Using and managing licenses
  • Reading and writing data
  • Using cryptographic functions

Our Runtime API is available as a dynamic library, as a .NET assembly, and as a Java interface. With these interfaces, all common programming languages can use our API, including C/C++, C#, C++/CLI, Delphi, Java, Fortran, Fortran, VB, VB.NET, and Python.

Fully documented API's

By using our API's software developers can determine how licenses are used in their software. Licenses can be checked when the software is launched, and individual features can then be activated, deactivated, or hidden depending on the available license. It can also be decided if licenses are allocated already during start-up or at the first usage of the corresponding function.


No. For 95% of all the protection and licensing functionalities your compiled software should be just fine in combination with our automatic wrapper. You can go ahead, protect your software quickly and release immediately with our toolset.
You can test-drive all API calls with our API guide. And of course, in our developer guide there’s extensive documentation. But if you really want the best and quickest implementation, ask for help from our professional services team. Our consultants work with our API on a daily basis and can inform you pretty precisely on how much time your custom requirements would need.
From a technical point of view: nothing. The automatic wrapper simply uses a generic but intricate subset of API calls. We have different levels of API calls; core API and amalgamated calls which could all be custom implemented if you prefer. But the automatic wrapper uses a standardized choice selection of the finest API calls our solution can serve.