Webhooks API

Name: Webhooks API API
Brand: Webhooks API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey9 EndpointsREST

For Agents

Configure a HubSpot app's webhook subscriptions and target URL so HubSpot pushes change events for CRM objects to your service.

Connect the Webhooks API to your agent

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

Configure the target URL HubSpot calls when subscribed events fire

Create event subscriptions on contact, company, deal, and ticket changes

Activate or deactivate individual subscriptions without deleting them

Batch-update subscription state for an app in a single call

GET STARTED

Start building with Webhooks API API

Explore with Jentic

View OpenAPI Document

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

Jentic publishes the only available OpenAPI specification for the HubSpot Webhooks API, keeping it validated and agent-ready. The Webhooks API lets a HubSpot app subscribe to change events on contacts, companies, deals, tickets, and other CRM objects. It manages subscription rules per app and configures the target URL HubSpot calls when matching events occur. Settings, individual subscriptions, and batch subscription updates are all managed through this surface.

Use Cases

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

★ Real-Time CRM Sync

Integrations that mirror HubSpot CRM data into another system (data warehouse, customer success platform, support tool) subscribe to creation, update, and deletion events. The Webhooks API configures the subscriptions and the target URL; HubSpot then POSTs event batches to the URL, and the integration applies the changes downstream within seconds rather than polling.

Create a subscription for app 12345 with subscriptionDetails type 'contact.propertyChange' and propertyName 'lifecyclestage', then activate it

Deal Pipeline Notification

Sales operations want notifications when deals move stages or close. The Webhooks API subscribes the app to deal.propertyChange events on dealstage and amount, and the target URL fans the events into Slack, email, or a custom dashboard. Tuning throttling in the settings endpoint controls how aggressively HubSpot batches and retries deliveries.

Create a subscription on event type 'deal.propertyChange' for propertyName 'dealstage' and configure target URL https://example.com/hooks/hubspot/deals

Bulk Subscription Management

Apps installed in many portals end up with dozens of subscriptions that need coordinated activation, pausing during maintenance windows, and bulk deletion when retired. The /subscriptions/batch/update endpoint changes active state across many subscriptions in one call, which is critical for keeping the deployment idempotent.

Call POST /webhooks/v3/{appId}/subscriptions/batch/update with the list of subscriptionIds and active set to false to pause delivery during maintenance

Agent-Driven Webhook Provisioning

An AI agent that owns a HubSpot app's deployment process uses Jentic to provision and reconcile webhook subscriptions. It searches for 'create hubspot webhook subscription', loads the schema, and posts the desired-state subscriptions; subsequent runs detect drift and PATCH or DELETE to converge on the configured set.

Search Jentic for 'create hubspot webhook subscription', load the schema, and reconcile the live subscriptions against the desired-state list for the app

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/webhooks/v3/{appId}/settings

Get the webhook target URL and throttling settings

PUT

/webhooks/v3/{appId}/settings

Update the webhook target URL and throttling

POST

/webhooks/v3/{appId}/subscriptions

Create a webhook subscription

GET

/webhooks/v3/{appId}/subscriptions

List webhook subscriptions for an app

PATCH

/webhooks/v3/{appId}/subscriptions/{subscriptionId}

Update a subscription

DELETE

/webhooks/v3/{appId}/subscriptions/{subscriptionId}

Delete a subscription

POST

/webhooks/v3/{appId}/subscriptions/batch/update

Batch-update subscription state

GET

/webhooks/v3/{appId}/settings

Get the webhook target URL and throttling settings

PUT

/webhooks/v3/{appId}/settings

Update the webhook target URL and throttling

POST

/webhooks/v3/{appId}/subscriptions

Create a webhook subscription

GET

/webhooks/v3/{appId}/subscriptions

List webhook subscriptions for an app

PATCH

/webhooks/v3/{appId}/subscriptions/{subscriptionId}

Update a subscription

Why though Jentic?

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

Credential isolation

HubSpot developer hapikeys are stored encrypted in the Jentic vault. Agents receive a scoped token at execution time and the raw developer key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g., 'create hubspot webhook subscription') and Jentic returns POST /webhooks/v3/{appId}/subscriptions with its input schema, including subscriptionDetails and active fields.

Time to first call

Direct HubSpot integration: 2-3 days for developer key setup, target URL plumbing, retry handling, and subscription reconciliation. Through Jentic: under 1 hour for the management API calls — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

HubSpot Events API

Webhooks deliver real-time change events; the Events API reads historical activity

Use Webhooks for streaming change notifications; use the Events API for backfills and timeline reconstruction.

Complementary

HubSpot CRM Cards

CRM cards extend the record UI that webhook events report changes against

Pair Webhooks (notify on change) with CRM Cards (display the latest data inside HubSpot's record UI).

Alternative

Zapier Natural Language Actions

Zapier offers prebuilt HubSpot triggers as a no-code alternative to native webhooks

Pick Zapier when the consumer wants no-code workflow building; pick HubSpot Webhooks when the integration owns the receiving service and needs full payload control.

FAQs

Specific to using Webhooks API API through Jentic.

Why is there no official OpenAPI spec for the HubSpot Webhooks API?

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

It uses the developer hapikey passed as a query parameter on every request, scoped to the developer account that owns the app. Jentic stores the developer key in its encrypted vault and provides agents with a scoped token at execution time so the raw key never enters the agent's context.

Can a single subscription cover multiple property changes?

No. Each subscription targets a single eventType plus optional propertyName. To watch several properties on the same object — for example dealstage, amount, and closedate on deals — create one subscription per property. Use POST /webhooks/v3/{appId}/subscriptions/batch/update to manage their active state together.

What are the rate limits for the HubSpot Webhooks API?

Standard developer API limits apply: 100 requests per 10 seconds per developer account for the management endpoints. The runtime delivery rate (events HubSpot sends to your target URL) is governed by the throttling settings on /webhooks/v3/{appId}/settings — typical limits are 1,000 events per 10 seconds per app.

How do I subscribe my app to contact creation events through Jentic?

Search Jentic for 'create hubspot webhook subscription', load the schema for POST /webhooks/v3/{appId}/subscriptions, and execute with subscriptionDetails of type 'contact.creation'. Then PUT /webhooks/v3/{appId}/settings with the target URL where HubSpot should deliver events.

Is the HubSpot Webhooks API free?

API access is included with HubSpot's developer programme, which is free to join. Webhooks are delivered to any portal that has installed the app, regardless of subscription tier; the throttling and event types available scale with the developer account.