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.
9 endpointsJentic publishes the only available OpenAPI specification for Webhooks API, keeping it validated and agent-ready. The HubSpot Webhooks API lets a HubSpot public app subscribe to change events on contacts, companies, deals, tickets, and other CRM objects, then receive event payloads at a single configured target URL. Apps can configure a target URL with a max-concurrent-requests cap, then create, list, update, or archive subscriptions to specific event types. Authentication uses the developer-account hapikey because subscription configuration is scoped to the developer's app, not an end customer portal.
9 endpointsStep 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 | shStep 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 instanceJentic 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.