---
title: "List events"
method: GET
path: "/api/v2/events"
tags: ["Events (Schedules)", "Enterprise"]
---

# List events

`GET /api/v2/events`

Gets all client scheduled events.

## Query parameters

- `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.
- `id` string — Filter results by column integer value. Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
- `rrule` string — Filter results by column string value. Valid filter predicates are `eq`, `~eq`, `neq`.
- `next_scheduled_at` string — Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
- `client_id` string — Filter results by column string-formatted uuid value. Valid filter predicates are `eq`, `neq`.
- `session_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `local_group_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `ad_structure_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `cert_services_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `ca_registry_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `dc_registry_collection` string — Filter results by column boolean value. Valid filter predicates are `eq`, `neq`.
- `hydrate_domains` boolean
- `hydrate_ous` boolean
- `created_at` string — Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
- `updated_at` string — Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
- `deleted_at` string — Filter results by column timestamp value formatted as an RFC-3339 string. Valid filter predicates are `eq`, `neq`, `gt`, `gte`, `lt`, `lte`.
- `skip` integer — The number of items to skip in a paginated response.
- `limit` integer — The limit of results requested by the client.

## Response `200`

OK

- object
  - `count` integer — The total number of results.
  - `skip` integer — The number of items to skip in a paginated response.
  - `limit` integer — The limit of results requested by the client.
  - `data` ModelClientScheduleDisplay[]
    - `id` integer — This is the unique identifier for this object.
    - `client_id` string, uuid
    - `rrule` string
    - `session_collection` boolean
    - `local_group_collection` boolean
    - `ad_structure_collection` boolean
    - `cert_services_collection` boolean
    - `ca_registry_collection` boolean
    - `dc_registry_collection` boolean
    - `all_trusted_domains` boolean
    - `ous` ModelOuDetails[]
      - `objectid` string
      - `name` string, nullable
      - `exists` boolean, nullable
      - `distinguishedname` string, nullable
      - `type` string, nullable
    - `domains` ModelDomainDetails[]
      - `objectid` string
      - `name` string, nullable
      - `exists` boolean, nullable
      - `type` string

## Other responses

- `400` — **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)
- `401` — **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).
- `403` — **Forbidden** This is most commonly caused by an authenticated client trying to access a resource that it does not have permission for.
- `500` — **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.

---

[API](https://skmtc.net/specterops/apis/bloodhound-api.md) · [All operations](https://skmtc.net/specterops/apis/bloodhound-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/specterops/bloodhound-api/revisions/b7bbf50b77e7/schema)