SpecterOps · jeff-matthews · Apr 9, 2026 · Mar 31, 2026 · Mar 31, 2026 · Mar 31, 2026
diff --git a/docs/analyze-data/configuration.mdx b/docs/analyze-data/configuration.mdx
@@ -10,6 +10,10 @@ This article explains the multiple tenant-wide configurations supported by Blood
 
 When enabled, BloodHound Enterprise will perform data reconciliation and retention. The configuration also allows for the changing of the default retention time. See [Data reconciliation and retention](/collect-data/enterprise-collection/data-retention).
 
+## API Key Expiration
+
+When enabled, BloodHound Enterprise will enforce expiration of API keys based on a configured rotation period. This configuration applies to personal API tokens, non-personal API tokens, and collector client API tokens. See [API key expiration](/manage-bloodhound/auth/api-key-expiration).
+
 ## Citrix RDP Support
 
 When enabled, BloodHound Enterprise will prevent false-positive CanRDP findings for Citrix VDAs.

diff --git a/docs/assets/image1-1.png b/docs/assets/image1-1.png
diff --git a/docs/assets/image1-2.png b/docs/assets/image1-2.png
diff --git a/docs/assets/image1-3.png b/docs/assets/image1-3.png
diff --git a/docs/assets/image1-5.png b/docs/assets/image1-5.png
diff --git a/docs/assets/image1-6.png b/docs/assets/image1-6.png
diff --git a/docs/assets/image1-7.png b/docs/assets/image1-7.png
diff --git a/docs/collect-data/enterprise-collection/create-collector.mdx b/docs/collect-data/enterprise-collection/create-collector.mdx
@@ -2,6 +2,8 @@
 title: Create a BloodHound Enterprise Collector Client
 ---
 
+import ApiKeyExpiration from '/snippets/auth/api-key-expiration.mdx';
+
 <img noZoom src="/assets/enterprise-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise only"/>
 
 ## Purpose
@@ -18,6 +20,8 @@ It should be used by BloodHound Enterprise (BHE) administrators when deploying S
 * Having deployed a BloodHound Enterprise Tenant
 * Logged in as a user role, which is authorized to create a new collector client, see [Administering users and roles](/manage-bloodhound/auth/users-and-roles)
 
+  <ApiKeyExpiration />
+
 ## Process
 
 1.  In the top right, click settings ⚙️ → **Administration**
@@ -36,10 +40,15 @@ It should be used by BloodHound Enterprise (BHE) administrators when deploying S
 <Frame>
   <img src="/assets/image-72.png" alt=""/>
 </Frame>
-5.  The pop-up window _Client Token Info_ will appear; follow the instructions in it - save the key before clicking **CLOSE**
+5.  The pop-up window _Client Token Info_ will appear; follow the instructions in it – save the API token and Token ID before clicking **CLOSE**. Both values are required for authentication and will only be shown once.
 <Frame>
   <img src="/assets/image-73.png" alt=""/>
 </Frame>
+
+<Warning>
+The API token and Token ID are only shown once. If you lose either value, you must regenerate them from the **Manage Clients** page.
+</Warning>
+
 ## Outcome
 
 The collector client will appear in the **Manage Clients** table with a **Status** of **Unconfigured**.

diff --git a/docs/docs.json b/docs/docs.json
@@ -540,6 +540,7 @@
                   "manage-bloodhound/auth/overview",
                   "manage-bloodhound/auth/users-and-roles",
                   "manage-bloodhound/auth/mfa",
+                  "manage-bloodhound/auth/api-key-expiration",
                   {
                     "group": "OIDC",
                     "pages": [

diff --git a/docs/get-started/security-boundaries/enterprise-security-overview.mdx b/docs/get-started/security-boundaries/enterprise-security-overview.mdx
@@ -124,6 +124,16 @@ All passwords configured locally expire every 90 days.
 * At least one number
 * At least one symbol (One of: !@#$%^&*)
 
+#### API Key Expiration
+
+Administrators can [configure expiration](/manage-bloodhound/auth/api-key-expiration) for all API keys in BloodHound Enterprise. This setting helps reduce long-lived credentials and supports internal compliance requirements.
+
+* New API keys expire after 90 days by default.
+* Administrators can configure expiration from 1 to 365 days.
+* Personal and non-personal API keys both follow the configured policy.
+* Collector clients authenticate using API keys, so they are also subject to expiration if this setting is enabled.
+* API key rotation is manual. Users must create replacement keys before existing keys expire.
+
 #### Brute Force Resistance
 
 Although BloodHound Enterprise does not lock a user out from attempted brute forcing, API calls against the BloodHound Enterprise authentication API are limited to one call per second, making a successful brute force attack impossible before a password rotation occurs.

diff --git a/docs/images/admin/create-token.png b/docs/images/admin/create-token.png
diff --git a/docs/images/admin/enable-api-key-expiration.png b/docs/images/admin/enable-api-key-expiration.png
diff --git a/docs/images/admin/generate-api-token.png b/docs/images/admin/generate-api-token.png
diff --git a/docs/images/admin/regenerate-auth.png b/docs/images/admin/regenerate-auth.png
diff --git a/docs/install-data-collector/install-azurehound/create-configuration.mdx b/docs/install-data-collector/install-azurehound/create-configuration.mdx
@@ -3,6 +3,8 @@ title: Create an AzureHound Configuration
 description: Learn how to create a configuration file for AzureHound Enterprise data collection.
 ---
 
+import ApiKeyExpiration from '/snippets/auth/api-key-expiration.mdx';
+
 <img noZoom src="/assets/enterprise-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise only"/>
 
 To complete the configuration process, you must have the following information:
@@ -145,6 +147,8 @@ Follow the steps below to create your AzureHound Enterprise configuration file u
 
       Continue to the next step when you have the **Token ID** and **Token**.
 
+      <ApiKeyExpiration />
+
   1. Enter the collector client's **Token ID**.
 
       ```text

diff --git a/docs/install-data-collector/install-sharphound/local-configuration.mdx b/docs/install-data-collector/install-sharphound/local-configuration.mdx
@@ -2,6 +2,8 @@
 title: SharpHound Enterprise Local Configuration
 ---
 
+import ApiKeyExpiration from '/snippets/auth/api-key-expiration.mdx';
+
 <img noZoom src="/assets/enterprise-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise only"/>
 
 The local configuration of SharpHound Enterprise occurs within two files: [settings.json](#settings-json) and [auth.json](#auth-json), their file paths can be found in the table below. Note that %AppData% is the directory of the service account: "C:\\Users\\SERVICE_ACCOUNT$\\AppData\\Roaming".
@@ -77,6 +79,8 @@ The following table outlines supported fields and their default values:
 
 auth.json is a plaintext JSON file that defines the credentials the service will utilize to authenticate to the BloodHound Enterprise API. Creating a new client or rotating the credentials of an existing one will provide you with the complete JSON structure used for a SharpHound Enterprise client.
 
+<ApiKeyExpiration />
+
 An example of the file:
 ```json
 {

diff --git a/docs/integrations/bloodhound-api/working-with-api.mdx b/docs/integrations/bloodhound-api/working-with-api.mdx
@@ -1,124 +1,166 @@
 ---
 title: Work With the BloodHound API
+description: Learn how to access and use the BloodHound API for integrations, automation, and general exploration.
+sidebarTitle: Work with the API
 ---
 
+import CopyApiToken from '/snippets/auth/copy-api-token.mdx';
+
 <img noZoom src="/assets/enterprise-AND-community-edition-pill-tag.svg" alt="Enterprise and Community Edition badge" />
 
-The BloodHound product family are API-first products, meaning everything functions on the underlying API layer. All data displayed in the portal, all commands given to SharpHound or AzureHound Enterprise collectors, and all data uploaded pass through the BloodHound APIs. Customers may utilize these APIs to extend the use of the BloodHound product to function with other tools in their environment. This article will show how to access the API and include some example use cases.
+BloodHound is an API-first product, which means core product functionality runs on the API layer. All data shown in the user interface, all commands sent to SharpHound Enterprise and AzureHound Enterprise collectors, and all uploaded data pass through the BloodHound APIs.
+
+You can use these APIs to integrate BloodHound with other tools and workflows in your environment.
 
-## API Documentation
+## API Explorer
 
-Our API reference is available [here](../../reference/).
+In addition to the [REST API reference](/reference/overview) on this site, BloodHound provides an **API Explorer** that provides interactive API documentation and testing capabilities.
 
-Additionally, API documentation is hosted utilizing Swagger behind authentication within your tenant environment. After logging in, you may access it by clicking the cog in the top right corner of your tenant and clicking **API Explorer.**
+The **API Explorer** is built using Swagger UI and is accessible from within your tenant after logging in. It allows you to browse available API endpoints, view request and response schemas, and make test API calls directly from the interface.
 
-<Frame>
-  <img src="/assets/image1-1.png" alt="API Explorer menu in the BloodHound UI" />
-</Frame>
+<Steps>
+  <Step title="Navigate to API Explorer">
+    1. Log in to your BloodHound tenant.
+    1. In the left menu, click **API Explorer**.
+  </Step>
+  <Step title="Explore API Endpoints">
+    1. Browse through the list of available API endpoints categorized by functionality.
+    1. Click an endpoint to view details such as required parameters, request body schema, and response schema.
+    1. Click **Try it out** to make test API calls on your tenant.
+  </Step>
+</Steps>
 
 ## Authentication
 
-The BloodHound API accepts two forms of authentication, each with its own limitations for security.
+The BloodHound API accepts two forms of authentication:
+
+- A JSON Web Token (JWT) is generated during login using your email address, password, and 2FA token (or through a SAML- or OIDC-based authentication flow). JWTs remain active for 8 hours and are primarily used for end-user access to the web application.
+
+- An API token and token ID pair is generated in the Administration interface. API tokens are primarily used for integrations and automation.å
+
+There are two methods for creating API tokens in BloodHound, each serving a different purpose:
+
+- Non-personal API tokens and token IDs for [integrations](/integrations), such as Splunk, ServiceNow, and Cortex XSOAR
+- Personal API tokens and token IDs for individual day-to-day use, such as [BloodHound Operator](https://www.youtube.com/watch?v=9Og-6_qyw_A)
+
+### API key expiration
+
+BloodHound Enterprise supports [API key expiration](/manage-bloodhound/auth/api-key-expiration) to help you align with internal security and compliance requirements. This setting controls how long API tokens remain valid.
+
+<Note>
+  You must manually create replacement tokens and update all dependent integration configurations before they expire. BloodHound does not automatically rotate API keys.
+</Note>
 
-* A JWT is generated through the login process using your email address, password, and 2FA token (or SAML-based authentication flow). These JWT tokens are active for 8 hours and are primarily for end-user access to the web-based application.
-* An API key/ID pair is generated within the Administration interface. These do not expire and are primarily for long-term API integrations.
+### Non-personal API tokens
 
-There are two methods for creating API key/ID pairs, each serving a different purpose:
+Administrators can create service accounts for API integrations. Service accounts are standard BloodHound user accounts that are not tied to a specific person. They are intended for use by applications and services that need to interact with the BloodHound API.
 
-* Non-personal API key/ID pairs for integrations like [Splunk](/integrations/splunk/siem/install)
-* [Personal API key/ID pairs](#create-a-personal-api-key-and-id-pair) for day-to-day use like [BloodHound Operator](https://www.youtube.com/watch?v=9Og-6_qyw_A)
+When you create a non-personal API token and token ID for a service account, the roles and permissions assigned to that account determine its API access.
 
-### Create a non-personal API key/ID pair
+To create a non-personal API token and token ID:
 
-Administrators can create non-personal BloodHound users solely meant for API integrations.
+<Steps>
+  <Step title="Create a new user account">
+    1. Log in as a user with the Administrator role.
 
-1. Log in as a user with the Administrator role.
-2. [Create a new BloodHound user](../../manage-bloodhound/auth/users-and-roles).
-   * Give the user a long and unique password.
-3. ***Optional recommendation:*** Log in as the newly created user and enable MFA.
-4. ***Optional recommendation:*** Securely dispose of the password and MFA configuration as they are not needed for authenticating with a key/ID pair and they can be reset by an Administrator if needed.
-5. As the Administrator, go back to the **Manage Users** page.
-6. On the API user, click the hamburger menu > **Generate / Revoke API Tokens**.
+    1. In the left menu, click **Administration** > **Manage Users**.
 
-<Frame>
-  <img src="/assets/image1-2.png" alt="Generate API Tokens" />
-</Frame>
+    1. Click **Create User** and enter the [required information](/manage-bloodhound/auth/users-and-roles).
 
-7. Click **Create Token**.
-8. Give the token a descriptive name and click **Save**.
-9. Save the presented API key/ID pair and click **Close**.
-   * **The API key will never be shown again. If you lose it, you must revoke the previous key and regenerate a new one.**
-10. You may now use this key ID pair for [calling the API](#call-the-api)
+    1. After creating the user, you may optionally log in as that user to enable MFA.
+
+       <Note>
+         MFA is not required for API key authentication, but it can provide an additional layer of security for the account.
 
-### Create a personal API Key and ID pair
+         If you choose to enable MFA, securely dispose of the password and MFA configuration after setup, as they are not needed for authenticating with API keys and can be reset by an Administrator if necessary.
+       </Note>
+  </Step>
+  <Step title="Generate an API token">
+    1. Log back in as an Administrator (if not already logged in).
 
-Create a personal API Key/ID pair from the **My Profile** section.
+    1. In the left menu, click **Administration** > **Manage Users**.
 
-1. <p>In the top-right corner click <Icon icon="gear" iconType="solid" /> <Icon icon="arrow-right" iconType="solid" /> **My Profile**.</p>
+    1. Find the user account you just created, click the hamburger menu, and select **Generate / Revoke API Tokens**.
 
-<Frame>
-  <img src="/assets/image1-3.png" alt="Create Token" />
-</Frame>
+        <Frame>
+          <img src="/images/admin/generate-api-token.png" alt="A view of the API token generation interface" />
+        </Frame>
 
-2. Click **API Key Management**.
 
-<Frame>
-  <img src="/assets/image1-7.png" alt="API Key Management" />
-</Frame>
+    1. Click **Create Token**, give it a descriptive name, and click **Save**.
 
-3. Click **Create Token**.
+    1. Save the API token and token ID and click **Close**.
 
-<Frame>
-  <img src="/assets/image1-4.png" alt="Create Token" />
-</Frame>
+        <CopyApiToken />
 
-4. Give the token a descriptive name and click **Save**.
+    1. Configure the dependent integration with the new API token and token ID.
+  </Step>
+</Steps>
 
-<Frame>
-  <img src="/assets/image1-5.png" alt="Create Token" />
-</Frame>
+### Personal API tokens
 
-5. Save the presented API key/ID pair and click **Close**.
-   * The API key will never be shown again. If you lose it, you must revoke the previous key and regenerate a new one.
+You can create personal API tokens and token IDs for your own use, such as for testing API calls. Personal API tokens are tied to your user account and inherit the permissions of that account.
 
-<Frame>
-  <img src="/assets/image1-6.png" alt="API Key Pair" />
-</Frame>
+To create a personal API token and token ID:
 
-Use this key/ID pair for calling the API.
+<Steps>
+  <Step title="Navigate to API Key Management">
+    1. Log in to your BloodHound tenant.
+
+    1. In the left menu, click **My Profile**.
+
+    1. Click **API Key Management**.
+  </Step>
+  <Step title="Generate an API token">
+    1. Click **Create Token**.
+
+        <Frame>
+          <img src="/images/admin/create-token.png" alt="A view of the API token creation interface" />
+        </Frame>
+
+    1. Give the token a descriptive name and click **Save**.
+
+    1. Save the API token and token ID and click **Close**.
+
+        <CopyApiToken />
+
+    1. Use the API token and token ID to call the API.
+  </Step>
+</Steps>
 
 ## Call the API
 
-Once you have your token, you can call the BloodHound API.
+After you have an API token and token ID, you can call the BloodHound API.
 
 ### Use a JWT/bearer token
 
 For quick tests or one-time calls, the JWT used by your browser may be the simplest route. The API accepts calls using the following header structure in the HTTP request:
 
-```json
+```
 'Authorization': Bearer $JWT_TOKEN
 ```
 
 If you open the **Network** tab in your browser, you'll see calls against the API made using this structure.
 
-### Use your API Key/ID pair
 
-For long-running API integrations, BloodHound's API uses hash-based message authentication code (HMAC) authentication using the API key as the secret key to verify the authenticity and integrity of the request. Calls against the API must include the following in the signed hash:
+### Use an API token
 
-* API key
+For long-running API integrations, BloodHound's API uses hash-based message authentication code (HMAC) authentication. The API token is used as the secret key to sign requests, and the token ID is sent as the identifier. Calls against the API must include the following in the signed hash:
+
+* API token
 * HTTP method and URI
 * Current time
 * Body content (if applicable to the request)
 
-Calls against the API would need to include the following headers in the HTTP request:
+Calls against the API must include the following headers in the HTTP request:
 
-```json
+```
 'Authorization': bhesignature $TOKEN_ID
 'RequestDate': $RFC3339_DATETIME
 'Signature': $BASE64ENCODED_HMAC_SIGNATURE
 ```
 
-By validating the hash signature against the request, the API can validate that the calls were made by the original requestor, within a reasonable timeframe, against the proper API endpoint, including the original content body, and that no replay or content modification has occurred.
+By validating the hash signature against the request, the API can ensure that calls were made by the original requestor, within a reasonable timeframe, against the proper API endpoint, including the original content body, and that no replay or content modification has occurred.
 
 For a complete implementation example, see [`apiclient.py`](https://github.com/SpecterOps/bloodhound-docs/blob/main/docs/assets/apiclient.py) in the `specterops/bloodhound-docs` GitHub repository. The following code snippet from the `apiclient.py` script illustrates the authentication process:
 

diff --git a/docs/integrations/cortex-xsoar/configure.mdx b/docs/integrations/cortex-xsoar/configure.mdx
@@ -4,6 +4,8 @@ description: Learn how to integrate BloodHound Enterprise with Cortex XSOAR by P
 sidebarTitle: Configure integration
 ---
 
+import ApiKeyExpiration from '/snippets/auth/api-key-expiration.mdx';
+
 <img noZoom src="/assets/enterprise-edition-pill-tag.svg" alt="Applies to BloodHound Enterprise only"/>
 
 The BloodHound Enterprise integration for [Cortex XSOAR](https://www.paloaltonetworks.com/resources/datasheets/cortex-xsoar-for-mssps#:~:text=Cortex%20XSOAR%C2%AE%EF%B8%8F%20is%20a,of%20services%20for%20their%20clients.) lets you ingest and manage BloodHound Enterprise attack path findings in Cortex XSOAR as incidents.
@@ -27,11 +29,11 @@ Key capabilities include:
 
 Before installing and configuring the Cortex XSOAR integration, ensure that you have the following:
 
-- Cortex XSOAR instance with an admin account
+- Admin access to a Cortex XSOAR instance
 - BloodHound Enterprise tenant
-- BloodHound Enterprise API key/ID pair
+- A BloodHound Enterprise [non-personal API token](/integrations/bloodhound-api/working-with-api#non-personal-api-tokens) with the **Auditor** role
 
-<Note>We recommend a [non-personal API key/ID pair](/integrations/bloodhound-api/working-with-api#create-a-non-personal-api-key%2Fid-pair).</Note>
+<ApiKeyExpiration />
 
 ## Configure Cortex XSOAR
 

diff --git a/docs/integrations/service-now/security-incident-response/configure.mdx b/docs/integrations/service-now/security-incident-response/configure.mdx
@@ -4,6 +4,7 @@ description: Learn how to install and configure the integration to automate the
 sidebarTitle: Install and configure
 ---
 
+import ApiKeyExpiration from '/snippets/auth/api-key-expiration.mdx';
 import InstallApp from '/snippets/integrations/servicenow-install.mdx';
 import CreateAppUser from '/snippets/integrations/servicenow-create-user.mdx';
 import ChangeAppScope from '/snippets/integrations/servicenow-change-app-scope.mdx';
@@ -26,7 +27,9 @@ Before you begin the installation and configuration process, ensure the followin
 - Admin access to a ServiceNow instance with the [Security Incident Response (SIR) module](https://www.servicenow.com/docs/r/security-management/security-incident-response/install-and-configure-sir.html) installed and configured
 - Access to the ServiceNow Store to install the BloodHound Enterprise app
 - Admin access to a BloodHound Enterprise tenant
-- A BloodHound Enterprise [non-personal API key/ID pair](/integrations/bloodhound-api/working-with-api#create-a-non-personal-api-key%2Fid-pair) with the **Auditor** role
+- A BloodHound Enterprise [non-personal API token](/integrations/bloodhound-api/working-with-api#non-personal-api-tokens) with the **Auditor** role
+
+<ApiKeyExpiration />
 
 ## Install the application