Getting The API Access Secret For Your Virtual Device

When connecting with Catnenis you will require both the Device ID and the Virtual Device’s API Secret Key. Each virtual device you create will have its own unique API Secret Key. Alternatively, you can set each device to use a Shared API Access Secret at the client level (see the section titled “Share Device Access Secret Across Multiple Virtual Devices”).

To Access the Virtual Device’s Access Secret Navigate to the virtual device by clicking on the “API ACCESS” link on the left navigation bar

You will then be presented with the “API ACCESS” screen.

Click on the “MANAGE VIRTUAL DEVICE”  button as all API access secrets are per virtual device at the device level.  Do not use the shared API access button. This button is only used when you have already configured your device(s) to share an API access secret (this is the box with a red X in figure 13)

Figure 13

You will now be presented with the Virtual Devices screen. Click on the Device ID of the Virtual device you wish to get the API access secret for (see figure 14)

Figure 14

You will now be presented with the device’s settings page. From the device settings page, click the “API ACCESS SECRET” button to view and/or reset the device’s API access secret(see figure 15).

Figure 15

Now you will be presented with the device’s API Access Secret (see figure 15a). Click “Copy to Clipboard” to retrieve the access secret for use in your bitcoin blockchain-enabled applications.

Figure 15a

To reset it, click the “RESET API ACCESS SECRET” button (see figure 15b).

Figure 15b

Resetting the device Access secret allows you to either reset the access secret at the device level or set the device to use the shared API access secret(see figure 16).

  1. (Optional) If the user wants to use the shared access secret for this given device, Check the “Reset device’s API access secret to shared API access secret” box to change it to the current shared API access secret.
  2. Type the phrase, “Yes, I do confirm it“.
  3. Click the “Confirm” button.
Figure 16

Related Articles