Webhook API

Name: Webhook API API
Brand: Webhook API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey10 EndpointsREST

For Agents

Subscribe to events emitted by Apideck Unified APIs, replay deliveries, and inspect event logs across CRM, HRIS, accounting, and other connectors.

Connect the Webhook API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webhook 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.

Install Jentic One Beta (Self-Hosted)

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

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 Webhook API API.

Create a webhook subscription pointed at your endpoint URL with selected event types

List, retrieve, update, and delete webhook subscriptions per consumer

Manually replay or execute a webhook for a given subscription and service via /execute or /x

Resolve and execute connection-level webhooks via /webhook/w/{id}/{serviceId}

GET STARTED

Start building with Webhook API API

Explore with Jentic

View OpenAPI Document

Use for: Create a webhook subscription for new contacts in the CRM Unified API, List all webhook subscriptions for this consumer, Update the delivery URL of an existing subscription, Delete a webhook subscription that is no longer needed

Not supported: Does not deliver inbound HTTP requests to your application directly, run workflow logic, or store custom field mappings — use only for managing webhook subscriptions, replaying deliveries, and inspecting event logs.

The Apideck Webhook API manages webhook subscriptions and delivery for events emitted by Apideck Unified APIs. Ten endpoints cover subscription CRUD, manual webhook execution against a specific service, callback resolution paths used by connectors that push events back, and event log retrieval for debugging. A subscription is identified by ID and scoped to a service, with execute and resolve endpoints allowing replay or on-demand delivery. Authentication uses the Apideck Authorization header alongside x-apideck-app-id and x-apideck-consumer-id.

Use Cases

Patterns agents use Webhook API API for, with concrete tasks.

★ Real-Time Sync Across Unified APIs

Receive events when records change in a customer's connected CRM, HRIS, or accounting system without polling. POST /webhook/webhooks creates a subscription tied to a consumer and event types; Apideck delivers normalised event payloads to the configured URL. Useful for keeping a SaaS product's local cache in sync with a customer's source-of-truth system.

Create a webhook subscription for consumer 'cust_42' on the 'crm' Unified API for events 'contact.created' and 'contact.updated' pointed at 'https://example.com/hooks/crm'

Webhook Replay and Backfill

Recover from downtime or a misconfigured handler by replaying missed webhooks. POST /webhook/webhooks/{id}/execute/{serviceId} fires a webhook on demand, and GET /webhook/logs surfaces past deliveries with their status. Useful for products that need a manual 'resync' button when an endpoint was returning errors.

List logs for subscription 'sub_42' filtered to status 'failed' in the last 24 hours and call POST /webhook/webhooks/sub_42/execute/{serviceId} for each to retry delivery

Event Log Inspection

Inspect every webhook delivery — outbound URL, status code, response body — to debug why a customer's integration is misbehaving. GET /webhook/logs returns the recent event log; subscription IDs and service IDs are returned with each entry so the failure can be traced to a specific connection.

Get the last 100 entries from GET /webhook/logs, group by subscription_id, and return a count of successful versus failed deliveries per subscription

AI Agent Webhook Setup via Jentic

An AI agent helps a customer wire up real-time sync. Through Jentic, the agent searches 'create a webhook subscription', loads the POST /webhook/webhooks operation, and executes it with the customer's URL and event filters. Jentic stores the Apideck Authorization, x-apideck-app-id, and x-apideck-consumer-id headers separately so the agent never holds raw credentials.

Through Jentic, search 'create a webhook subscription', load POST /webhook/webhooks, and create one for events 'contact.created' delivered to the URL the customer provides

Key Endpoints

10 endpoints — the apideck webhook api manages webhook subscriptions and delivery for events emitted by apideck unified apis.

METHOD

PATH

DESCRIPTION

GET

/webhook/webhooks

List webhook subscriptions

POST

/webhook/webhooks

Create a webhook subscription

PATCH

/webhook/webhooks/{id}

Update a webhook subscription

DELETE

/webhook/webhooks/{id}

Delete a webhook subscription

POST

/webhook/webhooks/{id}/execute/{serviceId}

Manually execute a webhook against a service

POST

/webhook/w/{id}/{serviceId}

Resolve and execute a connection webhook

GET

/webhook/logs

List webhook delivery event logs

GET

/webhook/webhooks

List webhook subscriptions

POST

/webhook/webhooks

Create a webhook subscription

PATCH

/webhook/webhooks/{id}

Update a webhook subscription

DELETE

/webhook/webhooks/{id}

Delete a webhook subscription

POST

/webhook/webhooks/{id}/execute/{serviceId}

Manually execute a webhook against a service

Why though Jentic?

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

Credential isolation

Apideck application keys, x-apideck-app-id, and x-apideck-consumer-id values are stored encrypted in the Jentic vault. Agents receive scoped execution tokens and never see the raw Authorization value, even when creating subscriptions or replaying deliveries.

Intent-based discovery

Agents search by intent (for example 'create a webhook subscription' or 'list webhook logs') and Jentic returns the matching Webhook operation with its input schema, so the agent calls POST /webhook/webhooks or GET /webhook/logs without consulting Apideck docs.

Time to first call

Direct Apideck Webhook integration: 1-2 days to wire subscription creation, signature verification, and replay handling. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Apideck Vault API

Vault stores the consumer connections that webhook subscriptions are scoped to.

Use Vault first to authorise the customer's connection; then create webhook subscriptions scoped to that consumer.

Complementary

Apideck CRM Unified API

CRM Unified API emits the events that webhook subscriptions deliver — contacts, deals, companies, etc.

Use CRM Unified for direct CRUD; use Webhook subscriptions for real-time push delivery of CRM changes.

Alternative

Pipedream API

Pipedream offers webhook-style triggers across thousands of apps with workflow execution attached.

Choose Pipedream when you also want workflow runtime; choose Apideck Webhook when sticking with Unified API event delivery.

FAQs

Specific to using Webhook API API through Jentic.

What authentication does the Apideck Webhook API use?

An apiKey scheme on the `Authorization` header with your Apideck application key, plus `x-apideck-app-id` and `x-apideck-consumer-id` headers. Through Jentic these are stored encrypted in the vault and injected at execution; the agent never sees the raw key.

Can I subscribe to events from multiple Unified APIs with one subscription?

Each subscription is created against a specific Unified API and event-type list via POST /webhook/webhooks. Create separate subscriptions for CRM, HRIS, accounting, etc. — list them all with GET /webhook/webhooks and update or delete individually.

What are the rate limits for the Apideck Webhook API?

The OpenAPI spec does not publish per-endpoint rate limits. Apideck applies plan-based limits at unify.apideck.com that cover both webhook management calls and outbound delivery throughput. See https://developers.apideck.com for your plan's gateway and event-delivery quotas.

How do I replay a missed webhook through Jentic?

Install with `pip install jentic`, then run the search query 'replay apideck webhook'. Jentic returns POST /webhook/webhooks/{id}/execute/{serviceId} — load its schema, supply the subscription ID and service ID for the missed delivery, then execute to retrigger.

How do I debug a webhook that is not arriving?

Call GET /webhook/logs to see recent delivery attempts with status codes and response bodies. If logs show 4xx/5xx responses from your endpoint, fix the handler and POST to /webhook/webhooks/{id}/execute/{serviceId} to replay. If no logs exist, double-check the subscription URL with GET /webhook/webhooks/{id}.

What's the difference between /execute and /w endpoints?

POST /webhook/webhooks/{id}/execute/{serviceId} (and the alias /webhook/webhooks/{id}/x/{serviceId}) manually fires a configured subscription. POST/GET /webhook/w/{id}/{serviceId} resolves and executes a connection-level webhook — used by connectors that push events back through Apideck rather than relying on a stored subscription.