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 Events (Schedules) API

The Events (Schedules) API from SpecterOps — 2 operation(s) for events (schedules).

SpecterOps Events (Schedules) API is one of 43 APIs that SpecterOps publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Events (Schedules). The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

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

Requests are made against a single base URL, /.

5 operations 2 paths 19 schemas 1 DELETE2 GET1 POST1 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 Events (Schedules) 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 5

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

Events (Schedules) 5
GET
/api/v2/events
List events
ListClientSchedules 19 params → 200400401403500
POST
/api/v2/events
Create Event
CreateClientSchedule 1 param body → 200400401403500
GET
/api/v2/events/{event_id}
Get Event
GetClientSchedule 2 params → 200400401403404500
PUT
/api/v2/events/{event_id}
Update Event
UpdateClientEvent 2 params body → 200400401403404500
DELETE
/api/v2/events/{event_id}
Delete Event
DeleteClientEvent 2 params → 200400401403404500

Schemas 19

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

model.client-schedule
api.error-detail
object
2 properties
null.time
object
2 properties
model.ou-details
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.uuid
string
Filter results by column string-formatted uuid value. Valid filter predicates are eq, neq.
api.params.predicate.filter.string
string
Filter results by column string value. Valid filter predicates are eq, ~eq, neq.
model.client-schedule-display
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.
api.params.query.skip
integer
The number of items to skip in a paginated response.
api.params.predicate.filter.integer
string
Filter results by column integer value. Valid filter predicates are eq, neq, gt, gte, lt, lte.
api.params.predicate.filter.boolean
string
Filter results by column boolean value. Valid filter predicates are eq, neq.
model.components.int32.id
object
1 property
api.response.pagination
object
3 properties
api.error-wrapper
object
4 properties
api.params.query.limit
integer
The limit of results requested by the client.
model.components.base-ad-entity
object
3 properties
model.components.timestamps
object
3 properties
model.domain-details

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

specterops-events-schedules-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 Attack Paths API
SpecterOps Audit API
SpecterOps Auth API
SpecterOps Azure Entities API
SpecterOps BloodHound Users API
Where this information came from

This is an independent, third-party profile of SpecterOps Events (Schedules) 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.