How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SpecterOps Attack Paths API

The Attack Paths API from SpecterOps — 10 operation(s) for attack paths.

SpecterOps Attack Paths API is one of 43 APIs that SpecterOps publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Attack Paths. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 10 operations across 10 paths, and defines 22 schemas. It is described by OpenAPI 3.2.0, at version v2.

Requests are made against a single base URL, /.

10 operations 10 paths 22 schemas 8 GET2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v2
Base URL
https://bloodhoundenterprise.io/api/v2
Authentication
HTTP Bearer, API Key, API Key, API Key
License
Resource Areas
1

Authentication & Security 4

SpecterOps Attack Paths API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (JWTBearerToken). An API key is passed in the header as Authorization (SignedRequest). An API key is passed in the header as RequestDate (RequestDate). An API key is passed in the header as Signature (HMACSignature). By default, every request must be authenticated.

  • JWTBearerToken — Authorization: Bearer $JWTTOKEN
  • SignedRequest — Authorization: bhesignature $TOKENID
  • RequestDate — RequestDate: $RFC3339DATETIME
  • HMACSignature — Signature: $BASE64ENCODEDHMACSIGNATURE

Paths & Operations 10

Across 10 paths, the API surfaces 10 operations — 8 GET, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Attack Paths 10
GET
/api/v2/domains/{domain_id}/attack-path-findingsdeprecated
Export attack path findings
ExportAttackPathFindings 5 params → 200400401403404429500
GET
/api/v2/attack-paths/finding-trends
List finding trends
FindingTrendsForEnvironment 5 params → 200400401403404429500
GET
/api/v2/attack-path-types
List all attack path types
ListAttackPathTypes 3 params → 200400401404429500
PUT
/api/v2/attack-paths
Start analysis
StartAnalysisBhe 1 param → 202401403429500
GET
/api/v2/attack-paths/details
Get all attack path findings
GetAllAttackPathFindings 1 param → 200400401403429500
GET
/api/v2/attack-paths/findings
List attack path findings
ListAttackPathFindings 23 params → 200400401403404429500
GET
/api/v2/domains/{domain_id}/available-types
List available attack paths
ListAvailableAttackPathTypesForDomain 5 params → 200400401403404429500
GET
/api/v2/domains/{domain_id}/details
List domain attack paths details
ListDomainAttackPathsDetails 22 params → 200400401403404429500
GET
/api/v2/domains/{domain_id}/sparkline
List attack path sparkline values
ListAttackPathSparklineValues 7 params → 200400401403429500
PUT
/api/v2/attack-paths/{attack_path_id}/acceptance
Update attack path risk
UpdateAttackPathRisk 2 params body → 200400401403404429500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are api.error-wrapper (4 properties), model.components.timestamps (3 properties), api.response.pagination (3 properties), api.error-detail (2 properties). Each schema is shown below with its type and property counts.

api.error-detail
object
2 properties
null.time
object
2 properties
model.relationship-finding
api.params.predicate.filter.time
string
Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are eq, neq, gt, gte, lt, lte.
api.params.predicate.filter.string
string
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
api.params.query.sort-by
string
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.list-finding
api.response.finding
object
1 property
model.components.int64.id
object
1 property
api.params.query.skip
integer
The number of items to skip in a paginated response.
api.response.all-findings
object
2 properties 2 required
enum.risk-acceptance
string
api.params.predicate.filter.integer
string
Filter results by column integer value. Valid filter predicates are eq, neq, gt, gte, lt, lte.
model.components.int32.id
object
1 property
api.response.time-window
object
2 properties
api.response.pagination
object
3 properties
null.int64
object
2 properties
api.error-wrapper
object
4 properties
model.risk-counts
api.params.query.limit
integer
The limit of results requested by the client.
model.components.timestamps
object
3 properties
model.unified-finding

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

specterops-attack-paths-api-openapi.yml Raw ↑

Other APIs SpecterOps publishes across the network.

SpecterOps AD Base Entities API
SpecterOps AD Users API
SpecterOps AIA CAs API
SpecterOps Analysis API
SpecterOps API Info API
SpecterOps API Tokens API
SpecterOps Asset Isolation API
SpecterOps Audit API
SpecterOps Auth API
SpecterOps Azure Entities API
SpecterOps BloodHound Users API
SpecterOps Cert Templates API
Where this information came from

This is an independent, third-party profile of SpecterOps Attack Paths API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.