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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fposthook.io%2Fposthook" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fposthook.io%2Fposthook" | 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

Replay completed webhook deliveries to re-trigger downstream processing

Cancel pending hooks individually or in bulk before their scheduled delivery time

GET STARTED

Start building with Posthook API

Explore with Jentic One

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

POST

/hooks/bulk/replay

Bulk replay completed hooks

POST

/hooks/bulk/cancel

Bulk cancel pending hooks

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Posthook API by hand means handling its X-API-Key header and formatting scheduling requests across its UTC, local-time, and relative-delay modes yourself. Through Jentic you install once, import the Posthook API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Posthook puts the hook id in the URL path (/hooks/{id}), so a rule can pin your agent to reading and scheduling hooks: you choose the operations it may call, so destructive ones like deleting a hook or bulk cancel are not included unless you add them.

Credential isolation

Your Posthook API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'schedule a webhook for later' or 'retry failed hooks', and Jentic returns the matching Posthook operation with its scheduling-mode parameters so the agent calls the right endpoint without browsing the reference docs.

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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Posthook API?

Yes. Jentic One is self-hosted, so you run your own instance and your own rules decide which Posthook operations and credentials the agent may use. Because Posthook puts the hook id in the URL path (/hooks/{id}), you can pin the agent to scheduling and reading hooks, such as POST /hooks and GET /hooks/{id}, while leaving out destructive calls like DELETE /hooks/{id} or the bulk cancel and bulk retry endpoints. Those operations are only available to the agent if you explicitly add them to its allowed set.

Posthook API

Name: Posthook API
Brand: Posthook API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticDeveloper ToolsCi CdapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

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.

Use for: I need to schedule a webhook delivery for a specific time, I want to retry all failed hooks from yesterday, Cancel a pending scheduled webhook, Get the details and status of a specific hook

Not supported: Does not handle webhook receiving, URL verification, or event source management - use for scheduling outbound webhook deliveries only.

Jentic publishes the only available OpenAPI specification for Posthook API, keeping it validated and agent-ready. Posthook API provides scheduled webhook delivery with configurable retry policies. It allows scheduling hooks for delivery at specific UTC timestamps, local times with timezone awareness, or relative delays up to 365 days. The API includes bulk operations for retrying failed hooks, replaying completed deliveries, and cancelling pending hooks, plus per-hook retry configuration with fixed or exponential backoff strategies.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

50%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

13%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

25%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

41%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

72%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

77%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Posthook API to your agent

Capabilities

Start building with Posthook API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Posthook API

Jentic AI Readiness Score

Posthook API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness