Posthook API

Name: Posthook API
Brand: Posthook API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsCi CdapiKey7 EndpointsREST

For Agents

Schedule webhook deliveries at specific times or relative delays, manage hook lifecycle with bulk retry, replay, and cancel operations, and configure per-hook retry strategies.

Install Jentic One Beta

Connect the Posthook API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Posthook API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Posthook API.

Schedule webhook deliveries at exact UTC timestamps, local times with timezone, or relative delays

Configure per-hook retry policies with fixed or exponential backoff up to 15 attempts

Retry failed hooks individually or in bulk using ID lists or time-range filters

GET STARTED

Start building with Posthook API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Posthook API for, with concrete tasks.

★ Scheduled Reminder and Notification Delivery

Schedule webhook callbacks at precise future times to trigger reminders, notifications, or time-delayed actions. Posthook supports UTC timestamps, timezone-aware local times, and relative delays (e.g., '2h30m'), with each hook carrying an arbitrary JSON payload. Hooks scheduled for past timestamps are delivered immediately.

Schedule a hook to POST to /webhooks/reminder with data containing user_id 123 at postAt 2026-07-01T09:00:00Z

Reliable Webhook Delivery with Retry

Ensure critical webhooks reach their destination by configuring per-hook retry strategies. Choose between fixed-delay and exponential backoff with up to 15 retry attempts, customizable delay (5-60 seconds), backoff factor (1.1-4.0), and optional jitter to prevent thundering herd issues when multiple hooks retry simultaneously.

Schedule a hook with retryOverride set to exponential strategy, 5 minRetries, 10 delaySecs, and backoffFactor 2.0

Bulk Recovery from Webhook Failures

Recover from outages by bulk-retrying failed hooks across a time range or by specific IDs. The bulk retry endpoint accepts up to 1000 hook IDs or a startTime/endTime filter with a limit, and returns the count of affected hooks. Similarly, bulk replay re-delivers completed hooks for reprocessing after downstream fixes.

Bulk retry all failed hooks between 2026-06-14T00:00:00Z and 2026-06-15T00:00:00Z with a limit of 500 using the /hooks/bulk/retry endpoint

AI Agent Webhook Scheduling via Jentic

AI agents use Jentic to discover Posthook operations by intent, such as 'schedule a delayed webhook' or 'retry failed webhooks'. Jentic returns the operation schema with parameters for scheduling modes (postAt, postAtLocal with timezone, or postIn for relative delay), then handles X-API-Key injection for authenticated delivery.

Search Jentic for 'schedule a delayed webhook', load the post_hooks schema, and execute with path '/callback', postIn '1h', and data payload

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for posthook api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/hooks

Schedule a new hook for future delivery

GET

/hooks

List hooks with filtering by status and time

GET

/hooks/{id}

Retrieve a single hook by ID

DELETE

/hooks/{id}

Cancel a pending hook

POST

/hooks/bulk/retry

Bulk retry failed hooks

POST

/hooks/bulk/replay

Bulk replay completed hooks

POST

/hooks/bulk/cancel

Bulk cancel pending hooks

POST

/hooks

Schedule a new hook for future delivery

GET

/hooks

List hooks with filtering by status and time

GET

/hooks/{id}

Retrieve a single hook by ID

DELETE

/hooks/{id}

Cancel a pending hook

POST

/hooks/bulk/retry

Bulk retry failed hooks

Why Jentic?

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

Credential isolation

Posthook X-API-Key credentials are stored encrypted in the Jentic vault. Agents receive scoped access so that webhook scheduling keys never appear in agent context or logs.

Intent-based discovery

Agents search by intent (e.g., 'schedule a webhook for later' or 'retry failed hooks') and Jentic returns the matching Posthook operation with parameters for scheduling mode selection (UTC, local time, or relative delay).

Time to first call

Direct Posthook integration: 1-2 days for scheduling logic, retry configuration, and bulk operation handling. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Posthook API through Jentic.

Why is there no official OpenAPI spec for Posthook API?

Posthook does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Posthook 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 Posthook API use?

The Posthook API uses an API key passed in the X-API-Key request header. Through Jentic, this key is stored in the encrypted credential vault and injected into headers automatically so agents never handle the raw key.

Can I schedule webhooks using relative time delays with the Posthook API?

Yes. The postIn parameter accepts a duration string such as '5m', '2h', '1d12h' combining days, hours, minutes, and seconds. The minimum delay is 1 second and maximum is 365 days. This is mutually exclusive with the postAt and postAtLocal parameters.

What are the rate limits for the Posthook API?

Posthook provides quota information in response headers: Posthook-HookQuota-Limit shows your billing period maximum, Posthook-HookQuota-Usage shows current usage, Posthook-HookQuota-Remaining shows remaining hooks, and Posthook-HookQuota-Resets-At indicates when the quota resets.

How do I configure retry behavior for individual webhooks?

Include a retryOverride object when scheduling a hook. Specify minRetries (1-15 attempts), delaySecs (5-60 seconds between attempts), and strategy ('fixed' or 'exponential'). For exponential backoff, set backoffFactor (1.1-4.0), maxDelaySecs (60-3600), and optionally enable jitter to randomize delays.

How do I bulk retry failed hooks through the Posthook API with Jentic?

Install the SDK with pip install jentic, then search for 'retry failed webhooks in bulk'. Jentic returns the post_hooks_bulk_retry operation schema. You can provide either a hookIDs array (up to 1000 IDs) or a time-range filter with startTime, endTime, and limit parameters to select which failed hooks to retry.

Posthook API

Connect the Posthook API to your agent

Capabilities

Start building with Posthook API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs