Smarx OS API

Implementing the API into the source code is aimed at professional software developers who require maximum security and flexibility for their protection strategy. For example, this is how you can deliver a limited demo version without a dongle, that automatically becomes the full version when attaching a valid  CRYPTO-BOX. Activate specific parts of the program - using the Remote Update Management System (RUMS) - after the customer has paid and/or requested additional features.

With the powerful Smarx^®OS system individual integration into the source code is possible under Windows, Linux and macOS. With our Smarx OS APIs you can fully exhaust the encryption features and access various hierarchies of the CRYPTO-BOX, including access to the internal flash memory and usage of pre-defined DataObjects, plus updating them directly at the end-users side. The intelligent memory management system of the Smarx interface enables multiple applications to simultaneously access the internal memory of the USB dongle. Each application has its own partition, accidental overwriting of data by another application is impossible. The Smarx interface supports both the local as well as network integration. Having the same function calls for Windows, Linux and macOS reduces the porting complexity of changing platforms. A wide range of compilers and development environments like Visual Studio. NET, Delphi and Java are supported.

Available APIs for Developers:

• Smarx API - API Abstraction Layer
  The Smarx API exposes a simple and user friendly programming interface to developers. In contrast other interfaces (SmarxCpp/Basic APIs for C++/Delphi or CBIOS4NET/Smarx4NET for C#, see below), this significantly reduces implementation efforts as well as chances of bugs and logical errors during implementation. At the same time, it provides developer with more flexibility on protection and licensing logic compared to AutoCrypt.

• AC API - API Abstraction Layer
  The recently introduced AC API is focused on the easiest possible implementation allowing developers with just one function call to start periodic validation of license data in the CRYPTO-BOX (e.g. Expiration Date or Execution Counter) for both local and network scenarios, plus adding an exit event notification (AppExitEvent) with exception argument. Therefore it is a good alternative when AutoCrypt is not applicable.
  AC API supports C++ and C# (Visual Studio 2013 or higher).

• CBIOS4NET/Smarx4NET and SmarxCpp - Object Oriented APIs
  For C++/C#/VB.NET developers, the following object oriented APIs are offered (Smarx4NET/CBIOS4NET for C# and VB, and SmarxCpp for C++):
  • Smarx4NET/CBIOS4NET - special Smarx OS API implementation for the .NET platform (.NET 2.0 and up, C# and VB).
  • SmarxCpp - object oriented Smarx OS API implementation for C++ developers. It is implemented as static library (MSVS2013 and higher) and dynamic library.

• Basic APIs (CBIOS/DO/RFP API)
  This is the core API set for the CRYPTO-BOX. You might consider it if either your IDE is not supported by one of the above APIs, or when you need full control/maximum flexibility:
  • CBIOS API - Commands used to access the CRYPTO-BOX (local or network), to the internal memory and the encryption functions (hardware-based AES or RSA* encryption). 
  • CBIOS DO API - Managing data objects in the memory of the CRYPTO-BOX, such as expiration date, network licenses, or customer specific objects. These data objects can be updated remotely (RUMS in SmarxOS Application Framework, or the RFP API) at a later time.
  • CBIOS RFP API - Updating DataObjects directly to the end-users site.

* CRYPTO-BOX SC only