SpecterOps · Authentication Profile

Specterops Authentication

Authentication

SpecterOps secures its APIs with apiKey and http across 4 declared security schemes, as derived from its OpenAPI definitions.

CompanyCybersecurityIdentityActive DirectoryAttack Path ManagementOffensive SecurityGraphBloodHound
Methods: apiKey, http Schemes: 4 OAuth flows: API key in: header

Security Schemes

JWTBearerToken http
scheme: bearer
SignedRequest apiKey
· in: header (Authorization)
RequestDate apiKey
· in: header (RequestDate)
HMACSignature apiKey
· in: header (Signature)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/specterops-bloodhound-openapi.json
docs: https://bloodhound.specterops.io/integrations/bloodhound-api/working-with-api
notes: 'Two mechanisms: JWT bearer (Authorization: Bearer $JWT, 8-hour TTL, via Login) and an HMAC-signed
  request using a non-expiring API key/ID pair (Authorization: bhesignature $TOKEN_ID + RequestDate +
  Signature; HMAC-SHA-256 chain over method+URI, RFC3339 date-to-hour, and body).'
summary:
  types:
  - apiKey
  - http
  api_key_in:
  - header
schemes:
- name: JWTBearerToken
  type: http
  scheme: bearer
  bearerFormat: JWT
  description: '`Authorization: Bearer $JWT_TOKEN`'
  sources:
  - openapi/specterops-bloodhound-openapi.json
- name: SignedRequest
  type: apiKey
  in: header
  parameter: Authorization
  description: '`Authorization: bhesignature $TOKEN_ID`'
  sources:
  - openapi/specterops-bloodhound-openapi.json
- name: RequestDate
  type: apiKey
  in: header
  parameter: RequestDate
  description: '`RequestDate: $RFC3339_DATETIME`'
  sources:
  - openapi/specterops-bloodhound-openapi.json
- name: HMACSignature
  type: apiKey
  in: header
  parameter: Signature
  description: '`Signature: $BASE64ENCODED_HMAC_SIGNATURE`'
  sources:
  - openapi/specterops-bloodhound-openapi.json