SpecterOps Custom Node Management API
The Custom Node Management API from SpecterOps — 2 operation(s) for custom node management.
OpenAPI Specification
openapi: 3.0.3
info:
title: BloodHound AD Base Entities Custom Node Management API
contact:
name: BloodHound Enterprise Support
url: https://bloodhound.specterops.io/
email: support@specterops.io
license:
name: Apache-2.0
url: https://www.apache.org/licenses/LICENSE-2.0
version: v2
description: "This is the API that drives BloodHound Enterprise and Community Edition.\nEndpoint availability is denoted using the `Community` and `Enterprise` tags.\n\nContact information listed is for BloodHound Enterprise customers. To get help with\nBloodHound Community Edition, please join our\n[Slack community](https://ghst.ly/BHSlack/).\n\n## Authentication\n\nThe BloodHound API supports two kinds of authentication: JWT bearer tokens and Signed Requests.\nFor quick tests or one-time calls, the JWT used by your browser may be the simplest route. For\nmore secure and long lived API integrations, the recommended option is signed requests.\n\n### JWT Bearer Token\n\nThe API will accept calls using the following header structure in the HTTP request:\n```\nAuthorization: Bearer $JWT_TOKEN\n```\nIf you open the Network tab within your browser, you will see calls against the API made utilizing\nthis structure. JWT bearer tokens are supported by the BloodHound API, however it is recommended\nthey only be used for temporary access. JWT tokens expire after a set amount of time and require\nre-authentication using secret credentials.\n\n### Signed Requests\n\nSigned requests are the recommended form of authentication for the BloodHound API. Not only are\nsigned requests better for long lived integrations, they also provide more security for the\nrequests being sent. They provide authentication of the client, as well as verification of request\nintegrity when received by the server.\n\nSigned requests consist of three main parts: The client token ID, the request timestamp, and a\nbase64 encoded HMAC signature. These three pieces of information are sent with the request using\nthe following header structure:\n\n```\nAuthorization: bhesignature $TOKEN_ID\nRequestDate: $RFC3339_DATETIME\nSignature: $BASE64ENCODED_HMAC_SIGNATURE\n```\n\nTo use signed requests, you will need to generate an API token. Each API token generated in the\nBloodHound API comes with two parts: The Token ID, which is used in the `Authorization` header,\nand the Token Key, which is used as part of the HMAC hashing process. The token ID should be\nconsidered as public (like a username) and the token key should be considered secret (like a\npassword). Once an API token is generated, you can use the key to sign requests.\n\nFor more documentation about how to work with authentication in the API, including examples\nof how to generate an API token in the BloodHound UI, please refer to this support doc:\n[Working with the BloodHound API](https://bloodhound.specterops.io/integrations/bloodhound-api/working-with-api).\n\n#### Signed Request Pseudo-code Example\n\nFirst, a digest is initiated with HMAC-SHA-256 using the token key as the digest key:\n```python\ndigester = hmac.new(sha256, api_token_key)\n```\n\nOperationKey is the first HMAC digest link in the signature chain. This prevents replay attacks that\nseek to modify the request method or URI. It is composed of concatenating the request method and\nthe request URI with no delimiter and computing the HMAC digest using the token key as the digest\nsecret:\n```python\n# Example: GET /api/v2/test/resource HTTP/1.1\n# Signature Component: GET/api/v2/test/resource\ndigester.write(request_method + request_uri)\n\n# Update the digester for further chaining\ndigester = hmac.New(sha256, digester.hash())\n```\n\nDateKey is the next HMAC digest link in the signature chain. This encodes the RFC3339\nformatted datetime value as part of the signature to the hour to prevent replay\nattacks that are older than max two hours. This value is added to the signature chain\nby cutting off all values from the RFC3339 formatted datetime from the hours value\nforward:\n```python\n# Example: 2020-12-01T23:59:60Z\n# Signature Component: 2020-12-01T23\nrequest_datetime = date.now()\ndigester.write(request_datetime[:13])\n\n# Update the digester for further chaining\ndigester = hmac.New(sha256, digester.hash())\n```\n\nBody signing is the last HMAC digest link in the signature chain. This encodes the\nrequest body as part of the signature to prevent replay attacks that seek to modify\nthe payload of a signed request. In the case where there is no body content the\nHMAC digest is computed anyway, simply with no values written to the digester:\n```python\nif request.body is not empty:\n digester.write(request.body)\n```\n\nFinally, base64 encode the final hash and write the three required headers before\nsending the request:\n```python\nencoded_hash = base64_encode(digester.hash())\nrequest.header.write('Authorization', 'bhesignature ' + token_id)\nrequest.header.write('RequestDate', request_datetime)\nrequest.header.write('Signature', encoded_hash)\n```\n"
servers:
- url: /
description: This is the base path for all endpoints, relative to the domain where the API is being hosted.
security:
- JWTBearerToken: []
- SignedRequest: []
RequestDate: []
HMACSignature: []
tags:
- name: Custom Node Management
paths:
/api/v2/custom-nodes:
parameters:
- $ref: '#/components/parameters/header.prefer'
get:
operationId: GetCustomNodes
summary: Get custom nodes
description: 'Retrieve a list of all custom node configurations.
This endpoint returns the current set of registered node kinds and their display settings.
'
tags:
- Custom Node Management
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/model.custom-node'
example:
data:
- id: 1
kindName: KindA
config:
icon:
type: font-awesome
name: house
color: '#FFFFFF'
- id: 2
kindName: KindB
config:
icon:
type: font-awesome
name: coffee
color: '#000000'
'401':
$ref: '#/components/responses/unauthorized'
'500':
$ref: '#/components/responses/internal-server-error'
post:
operationId: CreateCustomNodes
summary: Create custom nodes
description: 'This endpoint registers new node kinds along with optional display metadata such as icons and colors.
The provided configuration controls how nodes of the specified kinds are interpreted and rendered in the UI.
Only free, solid-style Font Awesome icons are supported. Hex color codes must follow the format #RGB or #RRGGBB.
If no valid icon or color is provided, the system will fall back to a question mark icon and a white background color.
Batch input is supported; you may submit multiple configuration objects in a single request.
'
tags:
- Custom Node Management
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
custom_types:
type: object
additionalProperties:
$ref: '#/components/schemas/model.custom-node.config'
example:
custom_types:
KindA:
icon:
type: font-awesome
name: house
color: '#FFFFFF'
KindB:
icon:
type: font-awesome
name: coffee
color: '#000000'
responses:
'201':
description: CREATED
content:
application/json:
schema:
type: object
properties:
data:
type: array
items:
$ref: '#/components/schemas/model.custom-node'
'400':
$ref: '#/components/responses/bad-request'
'401':
$ref: '#/components/responses/unauthorized'
'409':
description: '**Conflict**
Duplicate Kind Name
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 409
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: customnodes
message: 'Conflict: duplicate kind name'
'500':
$ref: '#/components/responses/internal-server-error'
/api/v2/custom-nodes/{kind_name}:
parameters:
- $ref: '#/components/parameters/header.prefer'
- name: kind_name
description: Kind Name
in: path
required: true
schema:
type: string
get:
operationId: GetCustomNode
summary: Get custom node
description: 'Retrieve the configuration for a specific custom node kind.
Returns the display settings and metadata for the requested node kind.
'
tags:
- Custom Node Management
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/model.custom-node'
example:
id: 1
kindName: KindA
config:
icon:
type: font-awesome
name: house
color: '#FFFFFF'
'401':
$ref: '#/components/responses/unauthorized'
'404':
$ref: '#/components/responses/not-found'
'500':
$ref: '#/components/responses/internal-server-error'
put:
operationId: UpdateCustomNode
summary: Update custom node
description: 'This endpoint updates an existing node kind along with optional display metadata such as icons and colors.
The provided configuration controls how nodes of the specified kinds are interpreted and rendered in the UI.
Only free, solid-style Font Awesome icons are supported. Hex color codes must follow the format #RGB or #RRGGBB.
If no valid icon or color is provided, the system will fall back to a question mark icon and a white background color.
'
tags:
- Custom Node Management
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
config:
$ref: '#/components/schemas/model.custom-node.config'
example:
config:
icon:
type: font-awesome
name: house
color: '#333'
responses:
'200':
description: OK
content:
application/json:
schema:
$ref: '#/components/schemas/model.custom-node'
'401':
$ref: '#/components/responses/unauthorized'
'404':
$ref: '#/components/responses/not-found'
'500':
$ref: '#/components/responses/internal-server-error'
delete:
operationId: DeleteCustomNode
deprecated: true
summary: Delete custom node (Deprecated)
description: '**Deprecated**: This endpoint is no longer supported and will return 410 Gone.
'
tags:
- Custom Node Management
responses:
'401':
$ref: '#/components/responses/unauthorized'
'410':
description: Gone - This endpoint has been deprecated
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
components:
responses:
not-found:
description: '**Not Found**
This error typically comes from operations where a valid ID was passed to the request
to look up an entity but the entity could not be found.
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 404
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: clients
message: The requested client could not be found.
bad-request:
description: '**Bad Request**
This could be due to one of the following reasons:
- JSON payload is missing or malformed
- Path or query parameters are missing or invalid/malformed
- The data sent is not valid (ex- sending a `string` in an `integer` field)
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 400
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: clients
message: The JSON payload could not be unmarshalled.
internal-server-error:
description: '**Internal Server Error**
This is usually the result of either an unexpected database or application error.
The client may try modifying or resending the request, but the error is likely not related to the client
doing something wrong.
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 500
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: clients
message: The request could not be handled due to an unexpected database error.
unauthorized:
description: '**Unauthorized**
This endpoint failed an authentication requirement. Either the client tried to access
a protected endpoint without being authenticated, or an auth validation failed (ex- invalid
credentials or expired token).
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 401
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: login
message: Unauthorized
schemas:
model.custom-node.config:
type: object
properties:
icon:
type: object
properties:
type:
type: string
name:
type: string
color:
type: string
api.error-detail:
type: object
properties:
context:
type: string
description: The context in which the error took place
message:
type: string
description: A human-readable description of the error
api.error-wrapper:
type: object
description: ''
properties:
http_status:
type: integer
description: The HTTP status code
minimum: 100
maximum: 600
timestamp:
type: string
format: date-time
description: The RFC-3339 timestamp in which the error response was sent
request_id:
type: string
format: uuid
description: The unique identifier of the request that failed
errors:
type: array
items:
$ref: '#/components/schemas/api.error-detail'
description: The error(s) that occurred from processing the request
model.custom-node:
type: object
properties:
id:
type: integer
kindName:
type: string
config:
$ref: '#/components/schemas/model.custom-node.config'
parameters:
header.prefer:
name: Prefer
description: Prefer header, used to specify a custom timeout in seconds using the wait parameter as per RFC7240. Passing in wait=-1 bypasses all timeout limits when the feature is enabled.
in: header
required: false
schema:
type: string
default: wait=30
pattern: ^wait=(-1|[0-9]+)$
securitySchemes:
JWTBearerToken:
description: '`Authorization: Bearer $JWT_TOKEN`
'
type: http
scheme: bearer
bearerFormat: JWT
SignedRequest:
description: '`Authorization: bhesignature $TOKEN_ID`
'
type: apiKey
name: Authorization
in: header
RequestDate:
description: '`RequestDate: $RFC3339_DATETIME`
'
type: apiKey
name: RequestDate
in: header
HMACSignature:
description: '`Signature: $BASE64ENCODED_HMAC_SIGNATURE`
'
type: apiKey
name: Signature
in: header
x-tagGroups:
- name: Community & Enterprise
tags:
- Auth
- Roles
- Permissions
- API Tokens
- BloodHound Users
- Collectors
- Collection Uploads
- Custom Node Management
- API Info
- Search
- Audit
- Config
- Asset Isolation
- Graph
- Azure Entities
- AD Base Entities
- Computers
- Containers
- Domains
- GPOs
- AIA CAs
- Root CAs
- Enterprise CAs
- NT Auth Stores
- Cert Templates
- OUs
- AD Users
- Groups
- Data Quality
- Datapipe
- Cypher
- OpenGraph (Experimental)
- name: Enterprise Only
tags:
- EULA
- BHE Users
- Analysis
- Client Ingest
- Clients
- Jobs
- Tasks
- Events (Schedules)
- Attack Paths
- Risk Posture
- Meta Entities
- Alerts