Developer Zone

License Management

Trackerbird allows you to maintain your own license key registry on the Trackerbird server in order to track license key usage and verify the status/validity of license keys used on your clients.

There are multiple ways by which the key registry is populated with license keys.

  1. Keys are collected automatically from your clients whenever you call the :cs:func:`TBApp.KeyChanged` method.
  2. You can add/edit keys manually via the Trackerbird web UI.
  3. You can upload keys in bulk using CSV files from the Trackerbird web UI.
  4. You can add/edit keys directly from your CRM by using the Trackerbird Web API.

Please check out this KBase article to learn about the correct file format when uploading keys to the Trackerbird Key Registry:

Client vs. Server Managed Licensing

Trackerbird gives you the option to choose between managing your license key status (i.e. Blacklisted, Whitelisted, Expired or Activated) and key type on the server (server managed) or managing this status youself through your client (client managed). ou can individually set whether each license status or license type is either Sever Managed or Client Managed by visiting the License Key Management Settings page on the Trackerbird web UI. The major difference is outlined below:

1- Client managed: The server licensing mechanism works in reporting-only mode and your application is expected to notify the server that the license status has changed through the use of :cs:func:`TBApp.SetLicense`.

When to use: You have implemented your own licensing module/mechanism within your application that can identify whether the license key used by this client is blacklisted, whitelisted, expired or activated. In this case you do not need to query the Trackerbird server to get this license status. However you can simply use this function to passively inform Trackerbird about the license status used by the client. In this case:

  1. Trackerbird will use this info filter and report the different key types and statuses and their activity.
  2. Trackerbird licensing server will operate in passive mode (i.e. reporting only).
  3. Calling :cs:func:`TBApp.KeyCheck` will return FunctionNotAvailable since the key status is client managed.

2- Server managed: You manage the key status on the server side and your application queries the server to determine the status of a particular license key by calling :cs:func:`TBApp.KeyCheck` or :cs:func:`TBApp.KeyChanged`.

When to use: If you do not have your own licensing module/mechanism within your application and thus you have no way to to identify the license status at the client side. In this mode, whenever a client changes their license key your application can call :cs:func:`tbKeyChanged` to register the new license key. In reply to this API call, the server will check if the license key exists on the key register and in the reply it will specify to your application whether this key is flagged as blacklisted, whitelisted, expired or activated, along with the type of key submitted. If you want to verify a key without actually registering a key change for this client you can use :cs:func:`TBApp.KeyCheck` which returns the same values but does not register this key with the server. In this case:

  1. The key register is maintained manually on the server by the software owner
  2. Trackerbird licensing server will operate in active mode so apart from using this key info for filtering and reporting, it will also report back the key status (validity) to the SDK whenever requested through the API.
  3. Calling :cs:func:`TBApp.KeyCheck` or :cs:func:`TBApp.KeyChanged` will return the 4 status flags denoting whether a registered key is: Blacklisted, Whitelisted, Expired and Activated and the key type.
  4. If the key does not exist on the server, all 4 status flags will be returned as false (0).