Black Kite third-party cyber risk intelligence (TPRM) platform provides non-intrusive, outside-in cyber risk ratings and assessments. It monitors organizations across 20+ risk categories including patch management, network security, application security, credential management, DNS health, email security, and ransomware exposure. For more information on Black Kite, refer here.
Integration Method: API
Tables: Entity Management (3004), Detection Finding (2004)
This integration supports the following events.
Event | Description |
|---|---|
Companies | This event retrieves company information that are monitored in black kite. |
Focus Tags | This event retrieves focus tag related information that are configured in black kite. |
Company Findings | This event retrieves company findings along with module specific information. |
This integration supports the following versions.
Black Kite API version | v2 |
Note:
Black Kite is a continuously updated service. As for this document preparation, the latest release was in June 1, 2026. More information can be found here.
Prerequisites
The user should have access to Black kite dashboard.
The user should have access to the DataBee console.
Configuration Overview
Generate client credentials in black kite.
Add the Black Kite in the DataBee console with the below parameters.
DataBee Parameter
Black Kite Parameter
Client Key
Client Secret
Token URL
This is the URL DataBee will interact with to get access token.
Black Kite Configuration
Login to Black Kite portal from here.
From the top navigation menu, click on Admin > Integrations Exchange.
In integration exchange, search for Black Kite API and click on it as shown below.
On “Integration Details” page, click on New Client Credential.
In the dialog box, provide description of credential to identify it, and select the access token life time as shown below. Preferrable life time is 1 hour.
Once credential details are provided, click on Next.
From the list of available roles, select Super User role to allow read access to tenant for fetching the required information via API and then click on Save.
Once client credential is created, copy the Client ID and Client Secret value as shown below to a safe place as they won’t be visible afterwards.
Note:
Once the client secret expires, a new secret must be generated and updated in DataBee to continue data ingestion.
DataBee Configuration
Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
Search for the Black Kite and click it as shown below.
Click on the API Ingest option for collection method.
Enter feed contact information and scroll down.
In the configuration page, confirm the following and click on Test Connection,
API Base URL: This is the base URL that DataBee will interact with.
Authorization Method: OAuth2
Token URL: This is the token URL that DataBee will interact with to get access token.
Client ID: Replace it with client id copied previously.
Client Secret: Replace it with client_secret copied previously.
Event Types: Preselected for all the event types that integration pulls.
Once test connection is successful, click on Submit.
Note:
If the test connection fails, the Submit button will remain disabled. Onboarding cannot proceed until the issue is resolved and the test connection is successful.
Troubleshooting Tips
Ensure the Client ID and Client Secret are pasted correctly. Since you cannot view the Client Secret after the 1st time, re-create the Client Secret, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.
Ensure the Black Kite roles/permissions are correct.