SpecterOps Audit API
The Audit API from SpecterOps — 1 operation(s) for audit.
The Audit API from SpecterOps — 1 operation(s) for audit.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/specterops-audit-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: BloodHound Audit 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.
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: Audit
paths:
/api/v2/audit:
parameters:
- $ref: '#/components/parameters/header.prefer'
get:
operationId: ListAuditLogs
summary: List audit logs
description: Returns a list of audit logs.
tags:
- Audit
parameters:
- $ref: '#/components/parameters/query.skip'
- $ref: '#/components/parameters/query.limit'
- $ref: '#/components/parameters/query.created-at'
- name: sort_by
description: 'Sortable columns are `id`, `actor_id`, `actor_name`, `actor_email`, `action`, `request_id`, `created_at`, `source`, and `status`.
'
in: query
schema:
$ref: '#/components/schemas/api.params.query.sort-by'
- name: before
description: Return logs created before the specified time. Value should be in the RFC-3339 format. If not supplied, this will default to the current time.
in: query
schema:
type: string
format: date-time
- name: after
description: Return logs created after the specified time. Value should be in the RFC-3339 format. If not supplied, this will default to 1 year before the current time.
in: query
schema:
type: string
format: date-time
- name: id
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: actor_id
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: actor_name
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: actor_email
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: action
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: request_id
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: source
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
- name: status
description: Filter results by column value. Valid filter predicates are `eq`, `neq`. Valid values are `success` and `failure`.
in: query
schema:
$ref: '#/components/schemas/api.params.predicate.filter.string'
responses:
'200':
description: OK
content:
application/json:
schema:
type: object
properties:
data:
type: object
properties:
logs:
type: array
items:
$ref: '#/components/schemas/model.audit-log'
'400':
$ref: '#/components/responses/bad-request'
'401':
$ref: '#/components/responses/unauthorized'
'403':
$ref: '#/components/responses/forbidden'
'429':
$ref: '#/components/responses/too-many-requests'
'500':
$ref: '#/components/responses/internal-server-error'
components:
responses:
forbidden:
description: '**Forbidden**
This is most commonly caused by an authenticated client trying to
access a resource that it does not have permission for.
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 403
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: clients
message: You do not have permission to access this resource
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
too-many-requests:
description: '**Too Many Requests**
The client has sent too many requests within a certain time window
and tripped the rate limiting middleware.
'
content:
application/json:
schema:
$ref: '#/components/schemas/api.error-wrapper'
example:
http_status: 429
timestamp: '2024-02-19T19:27:43.866Z'
request_id: 3fa85f64-5717-4562-b3fc-2c963f66afa6
errors:
- context: middleware
message: Too many requests. Please try again later.
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.
schemas:
api.params.query.limit:
type: integer
minimum: 0
description: The limit of results requested by the client.
model.audit-log:
allOf:
- $ref: '#/components/schemas/model.components.int64.id'
- type: object
properties:
created_at:
type: string
format: date-time
readOnly: true
actor_id:
type: string
format: uuid
readOnly: true
actor_name:
type: string
readOnly: true
actor_email:
type: string
format: email
readOnly: true
action:
type: string
readOnly: true
fields:
type: object
readOnly: true
request_id:
type: string
format: uuid
readOnly: true
source_ip_address:
type: string
format: ipv4
readOnly: true
commit_id:
type: string
format: uuid
readOnly: true
status:
readOnly: true
allOf:
- $ref: '#/components/schemas/enum.audit-log-status'
enum.audit-log-status:
type: string
enum:
- intent
- success
- failure
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.params.query.sort-by:
type: string
description: 'Sort by column. Can be used multiple times; prepend a hyphen for descending order.
See parameter description for details about which columns are sortable.
'
model.components.int64.id:
type: object
properties:
id:
type: integer
format: int64
readOnly: true
description: This is the unique identifier for this object.
api.params.predicate.filter.string:
type: string
pattern: ^((eq|~eq|neq):)?[^:]+$
description: 'Filter results by column string value. Valid filter predicates are `eq`, `~eq`, `neq`.
'
api.params.predicate.filter.time:
type: string
pattern: ^((eq|neq|gt|gte|lt|lte):)?[0-9]{4}-[0-9]{2}-[0-9]{2}[Tt][0-9]{2}:[0-9]{2}:[0-9]{2}(\.[0-9]{1,9})?([Zz]|-[0-9]{2}:[0-9]{2})$
description: 'Filter results by column timestamp value formatted as an RFC-3339 string.
Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
'
api.params.query.skip:
type: integer
minimum: 0
description: The number of items to skip in a paginated response.
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
parameters:
query.created-at:
name: created_at
in: query
description: Filter results by `created_at` value. See filter schema details for valid predicates.
schema:
$ref: '#/components/schemas/api.params.predicate.filter.time'
query.limit:
name: limit
description: This query parameter is used for setting an upper limit of objects returned in paginated responses.
in: query
schema:
$ref: '#/components/schemas/api.params.query.limit'
query.skip:
name: skip
description: This query parameter is used for determining the number of objects to skip in pagination.
in: query
schema:
$ref: '#/components/schemas/api.params.query.skip'
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