To generate an API key to authenticate with the Quin-C service, you will require a CodeMeter License dongle with the ADAPI tag (with current expiration date) applied as a license attribute of your AD Enterprise license.

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69009875822/original/tempsnip.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAS6FNSMY2XLZULJPI%2F20210926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210926T164104Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=c3ec2b8225cc15af0e465d46d194e4ddac1892d0326e5044fb5e0ff973458c06

There are 2 methods to generate keys, one through FTK / Lab / Enterprise and the other via the Quin-C interface (provided the browser has valid cookies cached). See the relevant section of this article that corresponds to how you wish to generate API keys.

API Key Generation (FTK / Lab / Enterprise)

As long as this dongle is plugged into the machine when you start the FTK.exe you will be able to generate API keys through the application. The FTK client has the ability to generate API keys by selecting the "Access API Key" option from the Tools menu item. 

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69009875823/original/mceclip0.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAS6FNSMY2XLZULJPI%2F20210926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210926T164104Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=2bc92f9dd436a514abde4434d364ec533c705a25822878debc49ab25ecb45959

In the new window that is created by selecting this option, you can select the user to generate an API key for. The user selection is used to define the permissions that the bound API key should obtain. Typically you will want to bind this to the Administrator so that the API key has access to all of the REST calls. By clicking "Generate Key", the text box above will populate with the relevant API key.

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69009875824/original/mceclip1.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAS6FNSMY2XLZULJPI%2F20210926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210926T164104Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=e3f2bde15828ccaa47dfb79adeaacd38e5ceafb113a45613488c6b32a83ab6a7


API Key Generation (Quin-C)

Once the dongle is plugged in and CodeMeter recognizes the device, the Quin-C service will be able to recognize the key. Simply logging into the Quin-C platform as normal will push validated cookies into your web browser, which is how the API key generation authenticates that it should release them. Upon logging into the Quin-C interface, go to the URL bar and we will need to manipulate the URL that Quin-C has redirected you too.

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69009875825/original/mceclip2.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAS6FNSMY2XLZULJPI%2F20210926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210926T164104Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=6f53245ddf4171db2dfad63f1e371ac53991a52fddc9323df942ff74b4049913

We must replace the ADGViewer.html#/review with api/security/{userid}/getenterpriseapiguid and we must replace the {userid} with the applicable userid for the user we logged in with. So to generate the Administrator's API key, the userid would be replaced with 1000. An example is shown below:

https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/69009875826/original/mceclip3.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAS6FNSMY2XLZULJPI%2F20210926%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20210926T164104Z&X-Amz-Expires=300&X-Amz-SignedHeaders=host&X-Amz-Signature=02bfb43ff52578d840a9335da49d5ed7c17b4837ba3cadfc18ed04e4da1b93c0