Hookdeck Admin REST API

Name: Hookdeck Admin REST API API
Brand: Hookdeck Admin REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring Observabilitybearer,basic116 EndpointsREST

For Agents

Inspect, replay, and configure webhook delivery on Hookdeck — sources, destinations, events, attempts, and bulk retries.

Quickstart

Get started with Hookdeck Admin REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"retry failed Hookdeck events"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Hookdeck Admin REST API API.

Configure sources and destinations to route inbound webhooks through Hookdeck

Inspect individual events and their delivery attempts to diagnose failures

Trigger bulk retries of failed events across a connection or filter window

Create issue triggers to alert on delivery failures, transformation errors, or backpressure

GET STARTED

Start building with Hookdeck Admin REST API API

Explore with Jentic

View OpenAPI Document

Use for: Find all events that failed delivery in the last hour, Retry every failed event for the stripe-prod connection, Get the full attempt history for a specific event, Create an issue trigger that pages on-call when a destination is down

Not supported: Does not handle outbound webhook delivery to your customers, payment processing, or message queue management — use for managing inbound webhook gateway operations only.

Jentic publishes the only available OpenAPI document for Hookdeck Admin REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Hookdeck Admin REST API, keeping it validated and agent-ready. The Hookdeck Admin REST API manages every primitive in a Hookdeck event gateway: sources, destinations, connections, transformations, issue triggers, bookmarks, requests, events, attempts, and bulk retry operations. It supports filtering and replaying webhook traffic, building custom alerting on delivery issues, and inspecting every attempt against a destination. Useful for SRE teams running webhook-heavy systems and AI agents that diagnose delivery failures.

Use Cases

Patterns agents use Hookdeck Admin REST API API for, with concrete tasks.

★ Webhook Failure Triage Agent

Run an SRE agent that watches Hookdeck for failed webhook deliveries, groups them by destination, and decides whether to retry, escalate, or open a ticket. The agent calls GET /events with a filter on status=failed, inspects attempts via GET /attempts/{id}, and triggers bulk retries when a transient outage clears. Cuts mean time to recovery on webhook outages.

List failed events for connection_id=conn_123 in the last hour, then call POST on the bulk retry events resource to replay them.

Webhook Onboarding Automation

Automate onboarding of new webhook sources for partner integrations. The agent calls POST /sources to register a new ingest URL, POST /destinations to point at the customer's endpoint, and ties them together with a connection. Replaces manual dashboard clicking when adding a new partner integration.

Create source 'partner-acme', destination pointing at https://acme.example.com/hooks, and a connection joining them.

On-Call Alerting From Issue Triggers

Wire Hookdeck issue triggers into an on-call rotation. The agent creates issue triggers via POST /issue-triggers for delivery failures or transformation errors, with a payload that posts to PagerDuty or Slack. Engineers stop missing webhook outages buried in dashboards.

Create an issue trigger that fires when a destination has more than 10 failed attempts in 5 minutes and POST it via /issue-triggers.

Replay Production Webhooks Locally

Bookmark interesting production events in Hookdeck and replay them against a local environment via the trigger endpoint. The agent calls POST /bookmarks/{id}/trigger to fire the bookmarked event on demand. Speeds up debugging webhook-driven flows without waiting for the next live event.

List bookmarks tagged 'failed-checkout', then trigger bookmark id bk_456 against the local development destination.

AI Webhook Operations Agent via Jentic

Expose Hookdeck's 116 endpoints to an AI ops agent through Jentic. The agent finds the right operation via intent search ('retry failed events for stripe connection'), Jentic loads the schema, and the agent executes with bearer auth handled in the MAXsystem vault.

Search Jentic for 'bulk retry failed events', load the schema, and execute against connection_id=conn_prod for the last 30 minutes.

Key Endpoints

116 endpoints — jentic publishes the only available openapi specification for hookdeck admin rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/events

List events with filtering by status and connection

GET

/attempts

List delivery attempts across events

POST

/sources

Create a new inbound source

POST

/destinations

Create a new outbound destination

POST

/issue-triggers

Create an alerting issue trigger

POST

/bookmarks/{id}/trigger

Replay a bookmarked event

GET

/connections

List source-to-destination connections

GET

/events

List events with filtering by status and connection

GET

/attempts

List delivery attempts across events

POST

/sources

Create a new inbound source

POST

/destinations

Create a new outbound destination

POST

/issue-triggers

Create an alerting issue trigger

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Hookdeck bearer keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped execution rights — the raw token never enters the agent's prompt window.

Intent-based discovery

With 116 endpoints, picking the right call by reading docs is slow. Agents search Jentic by intent (e.g., 'bulk retry failed events') and receive the matching operation directly.

Time to first call

Direct integration with Hookdeck's 116 endpoints: a few days to wire up auth, pagination, retry logic, and idempotency. Through Jentic: under an hour for the first call.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Svix API

Webhook-as-a-service platform focused on outbound delivery for SaaS providers.

Choose Svix when you are sending webhooks from your product to customers, rather than receiving and triaging inbound webhooks.

Complementary

ngrok API

Tunnels local services to the public internet for webhook development.

Pair ngrok with Hookdeck when an agent needs to forward Hookdeck destinations to a local dev environment for testing.

Complementary

Pipedream API

Workflow runtime that consumes webhooks and orchestrates multi-step automations.

Use Pipedream when you need a full workflow engine downstream of Hookdeck, not just delivery and retry.

FAQs

Specific to using Hookdeck Admin REST API API through Jentic.

Why is there no official OpenAPI spec for Hookdeck Admin REST API?

Hookdeck does not publish a maintained public OpenAPI specification for the admin REST API. Jentic generates and maintains this spec so that AI agents and developers can call Hookdeck Admin REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Hookdeck Admin REST API use?

The API supports bearer token auth (preferred) and HTTP basic. Generate an API key in the Hookdeck dashboard and pass it as Authorization: Bearer <key>. Jentic stores the key in the MAXsystem vault so agents never see the raw token.

Can I bulk retry failed webhooks with the Hookdeck Admin REST API?

Yes. The Bulk retry events resource accepts a filter (connection_id, time window, status) and replays every matching event. Bulk retry requests works the same way for inbound requests. Useful when an upstream destination recovers from an outage.

What are the rate limits for the Hookdeck Admin REST API?

Hookdeck applies workspace-level rate limits that scale with plan tier. Honor 429 responses and use the bulk retry resources rather than looping single retries — bulk operations count as one request even when they cover thousands of events.

How do I create an issue trigger with the Hookdeck Admin REST API through Jentic?

Run pip install jentic, search for 'create Hookdeck issue trigger', load the POST /issue-triggers schema, and execute with the trigger config (event type, channel, threshold). Jentic injects the bearer key for you.

Can I replay a single event with the Hookdeck Admin REST API?

Yes. Bookmark the event via POST /bookmarks, then trigger the replay with POST /bookmarks/{id}/trigger. This sends the bookmarked payload through the configured connection again — handy for debugging without waiting for a live event.