Managing an API token

To be able to use the Kaspersky Threat Intelligence Portal API, you must sign in by using the Kaspersky Account, and then request an API token (hereinafter also referred to as "token").

You can request, view, and revoke your token. The generated token is used as the header parameter X-API-KEY when you run requests by using the Kaspersky Threat Intelligence Portal API.

If you revoke the token, it becomes invalid, and cannot be used for working with the Kaspersky Threat Intelligence Portal API.

The maximum token validity period is one year.

Requesting a token

To request a token:

  1. Open Kaspersky Threat Intelligence Portal at https://opentip.kaspersky.com.
  2. Make sure you are signed in with your Kaspersky Account.
  3. In the <your email address> (User button.) drop-down menu, click Request token.

    The Request API Token page opens.

  4. If necessary, specify a validity period or expiration date for the token by using the calendar.

    By default, one year is specified.

    The validity period for the token cannot be changed after it is generated. You can only request another token, and then specify a new required date.

  5. Click the Request token button.

    The generated token appears in the text field. You can view your token at any time on the Request API Token page.

    Information about the token's validity period is displayed below the text field. A warning is displayed if there is less than one week left until the token expires.

  6. If necessary, you can copy the token by clicking the Copy to clipboard button.

Revoking a token

To revoke a token:

  1. Open Kaspersky Threat Intelligence Portal at https://opentip.kaspersky.com.
  2. Make sure you are signed in with your Kaspersky Account.
  3. In the <your email address> (User button.) drop-down menu, click Request token.

    The Request API Token page opens.

  4. Click the Revoke Token button.

    The token becomes invalid.

    To be able to work with the Kaspersky Threat Intelligence Portal API again, you must generate a new token.

Page top