Hubspot APIs

93 APIs957 Endpoints12 Categories

API Catalog(6 of 93)

Account Account Info

The HubSpot Account Info API exposes account-level metadata and private app API usage for a HubSpot portal. GET /account-info/v3/details returns the portal id, time zone, currency, company name, and whether the account is sandbox, while GET /account-info/v3/api-usage/daily/private-apps returns the day's call counts for each private app on the portal. The endpoints are designed for ops dashboards and quota monitoring rather than data manipulation. Both calls accept an OAuth 2.0 access token or a private app token in the private-app header.

2 endpoints

Account Test Child Api

The HubSpot Account Test Child API is a small surface that returns account-level activity, daily API usage, account details, and security events for a HubSpot portal. The four endpoints under /account-info/v3 are GET-only and read the same portal metadata used by ops dashboards and security tooling. Authentication uses the legacy OAuth scheme or a legacy private app token in the private-app-legacy header. The API is read-only and is intended for monitoring rather than configuration.

4 endpoints

CRM App Uninstalls

The HubSpot CRM App Uninstalls API provides a single endpoint for triggering an external uninstall of a HubSpot app integration. Calling DELETE /appinstalls/v3/external-install removes the app's installation record for the calling account, useful for offboarding flows and self-service customer-led teardown of an integration. The API is narrow and intended for app lifecycle automation rather than data CRUD.

1 endpoints

HubSpot Webhooks

The HubSpot Webhooks API configures the change-event subscriptions that a HubSpot app pushes to a target URL. It manages the app-level webhook settings such as target URL and throttling, and the per-event subscriptions for specific objects and event types. Subscriptions can be created, paused, batch updated, and deleted so apps stay aligned with the HubSpot data they need to react to in near real time.

9 endpoints

Public App Crm Cards

The HubSpot Public App CRM Cards API lets a public HubSpot app declare and manage the custom cards it surfaces in the sidebar of CRM record pages. Each card is registered up-front against an app ID with a target object type, a fetch URL HubSpot calls when a record is opened, and a definition of the actions and properties to render. Endpoints cover create, read, update, and delete of cards under a given app, plus a sample response endpoint that returns a representative payload so app developers can build a matching fetch handler. Use it to build product integrations that show external data — open invoices, ticket counts, account health — directly inside the HubSpot CRM UI.

6 endpoints

Public App Feature Flags V3

The HubSpot Public App Feature Flags V3 API lets developers of HubSpot public apps roll out features gradually by toggling per-account flag states. Developers define a feature flag at the app level and then enable, disable, or query the flag state for individual HubSpot portals (accounts) using the app. The API supports single-portal updates, batch upserts, batch deletes, and lookups across all portals where a flag has been set, making it suitable for staged rollouts, A/B experiments, and emergency feature kill switches.

9 endpoints

Connect Your Agent

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.