Hookdeck

Hookdeck Operator Events API

Operator events are Outpost's own lifecycle and alerting stream: delivery failures, destinations being auto-disabled, retry exhaustion and tenant subscription changes. They are about the deployment, not about a tenant's traffic, so they are delivered to **operator event destinations** rather than to tenant destinations. An operator event destination is deployment-wide, is not owned by any tenant you create, and has the same shape as a tenant destination: any destination type listed by `GET /operator-events/destination-types`, with that type's `config` and `credentials`. The Operator Events API is only available on managed Outpost, and requires the Admin API Key. Self-hosted deployments configure the same thing through environment variables and a single sink. See the [Operator Events](https://hookdeck.com/docs/outpost/features/operator-events) feature page. **Available topics** | Topic | Trigger | |-------|---------| | `alert.destination.consecutive_failure` | Consecutive failure count reaches 50%, 70%, 90%, or 100% of `ALERT_CONSECUTIVE_FAILURE_COUNT` | | `alert.destination.disabled` | Destination auto-disabled at the 100% failure threshold | | `alert.attempt.exhausted_retries` | Delivery exhausts all retry attempts | | `attempt.success` | Every successful delivery attempt | | `attempt.failed` | Every failed delivery attempt, including retries | | `tenant.subscription.updated` | A destination was created, updated or deleted and the tenant's topics or destination count changed | A destination may subscribe to every topic with `["*"]`, but `attempt.success` and `attempt.failed` fire once per delivery attempt and will dominate volume. Prefer an explicit topic list. **Topics are derived from these destinations.** The union of every enabled operator event destination's `topics` is what the deployment subscribes to, which is why `PATCH /config` rejects `OPERATOR_EVENTS_TOPICS` with a 422: change the destinations and the configuration follows.

Documentation GitHub OpenAPI

Operations 14

GET /operator-events/destination-types List Operator Event Destination Type Schemas #

GET /operator-events/destinations List Operator Event Destinations #

POST /operator-events/destinations Create Operator Event Destination #

GET /operator-events/destinations/{destination_id} Get Operator Event Destination #

PATCH /operator-events/destinations/{destination_id} Update Operator Event Destination #

DELETE /operator-events/destinations/{destination_id} Delete Operator Event Destination #

PUT /operator-events/destinations/{destination_id}/enable Enable Operator Event Destination #

PUT /operator-events/destinations/{destination_id}/disable Disable Operator Event Destination #

GET /operator-events/events List Operator Events #

GET /operator-events/events/{event_id} Get Operator Event #

GET /operator-events/events/{event_id}/attempts List Attempts for an Operator Event #

GET /operator-events/attempts List Operator Event Attempts #

GET /operator-events/attempts/{attempt_id} Get Operator Event Attempt #

POST /operator-events/retry Retry Operator Event Delivery #

Documentation

📖

Documentation

https://hookdeck.com/docs/bulk-retries

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/hookdeck/refs/heads/main/openapi/hookdeck-operator-events-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

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.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/hookdeck:hookdeck-operator-events-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Outpost Operator Events API
  version: 0.0.1
  description: 'The Outpost API is a REST-based JSON API for managing tenants, destinations, and publishing events.


    Outpost runs in two deployment models: **managed** (hosted by Hookdeck) and **self-hosted**. They differ in where the API is served and in which API key authenticates server-side calls. On managed Outpost, use a Hookdeck project API key from your Outpost project. On self-hosted Outpost, use the key set in the `API_KEY` environment variable. A few endpoints exist in one model only and say so in their description.'
  contact:
    name: Outpost Support
    email: support@hookdeck.com
    url: https://hookdeck.com/docs/outpost
servers:
- url: https://api.outpost.hookdeck.com/2025-07-01
  description: Managed Outpost, hosted by Hookdeck at `api.outpost.hookdeck.com`. The Hookdeck Event Gateway API at `api.hookdeck.com` is a separate API.
- url: http://localhost:3333/api/v1
  description: Self-hosted Outpost, at its default local address. A deployed instance serves the same paths under its own host.
security:
- AdminApiKey: []
- TenantJwt: []
tags:


# --- truncated at 32 KB (92 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/hookdeck/refs/heads/main/openapi/hookdeck-operator-events-api-openapi.yml