The API Report CardAPI Index
HubSpot Service Hub

HubSpot Service Hub API

hubspot.com

Service Hub rides HubSpot's public REST API: full ticket CRUD, search, and batch endpoints plus a Conversations API for threads. Access is self-serve with a free sandbox via OAuth or private app tokens. Help desk thread comments move to CRM notes in September 2026.

Last verified: July 2026Marketing & Sales
API GRADE
A
VERIFIED JUL 2026

SCORECARD

ExistenceGOODFull REST surface for tickets (CRM v3) and conversations at developers.hubspot.com, with batch and search endpoints.
AccessGOODSelf-serve developer account with free sandbox; private app tokens need no approval, marketplace apps do.
CoverageGOODTickets, threads, messages, and associations are all reachable; channels auto-create tickets with no API toggle.
AuthGOODOAuth 2.0 with granular scopes (tickets, conversations.read/write) or private app tokens for internal use.
Docs & DXGOODOfficial SDKs in five languages and published rate limits; Conversations docs are split across guides and changelogs.
StabilityGOODHelp Desk thread comments are deprecated for September 2026 with a documented migration path to the Notes API.
Supergood: HubSpot Service Hub shipped a real API. Most vendors don't; we ship near-native APIs for the rest.

Frequently asked questions

HubSpot Service Hub scores A on the API Report Card. Service Hub rides HubSpot's public REST API: full ticket CRUD, search, and batch endpoints plus a Conversations API for threads. Access is self-serve with a free sandbox via OAuth or private app tokens. Help desk thread comments move to CRM notes in September 2026.

Tried to integrate with HubSpot Service Hub?
SOURCES
Daily request limit is shared across all private apps in a HubSpot account (250k Free/Starter, 650k Pro, 1M Enterprise), so a single chatty integration can starve every other internal automation, and the cap forces upgrade to higher tiers or the paid API Limit Increase add-on developers.hubspot.com β†—
Breaking change in flight: Conversations API thread comments are being deprecated for Help Desk-typed inboxes and replaced by CRM notes effective September 23, 2026, integrations posting comments to help desk threads must migrate to the Notes API or break developers.hubspot.com β†—
Community threads report tickets created via the Tickets API don't always display correctly in the Help Desk UI with their associated conversation threads, requires additional setup to associate ticket-to-conversation-to-channel properly community.hubspot.com β†—
Conversations API documentation has historically been thin/in-beta and is split across multiple guides (Conversations v3 guide, Custom Channels API, Help Desk-specific behavior), requiring stitching across changelog posts to get a complete integration picture community.hubspot.com β†—
Help desk channels always auto-create tickets, the only way to prevent ticket creation from a channel is to disconnect the channel entirely, with no API toggle knowledge.hubspot.com β†—
Burst rate limit (100-190 req/10s per private app by tier) is aggressive enough that high-throughput sync workloads (e.g., backfilling tickets to a warehouse) commonly hit 429s and require client-side backoff/queueing scopiousdigital.com β†—
HubSpot continues to migrate from v1/v2 to v3 endpoints with periodic deprecation announcements; integrations built on legacy endpoints periodically require migration work developers.hubspot.com β†—
G2 reviewers report ticket management feels cumbersome and that core help desk functionality lags dedicated competitors, with limited ability to customize ticket properties per pipeline g2.com β†—
Multiple reviews cite 'poor UX for support ticketing, lacking in core functionality, behind the curve on AI capabilities' versus Zendesk, Freshdesk, and Intercom g2.com β†—
Switching between contacts, tickets, and notes takes extra clicks; the flow could be more streamlined for service-focused tasks (vs. dedicated help desks where the agent surface is single-pane) g2.com β†—
No visibility into chatbot conversations before they are handed off to a human, and contacts are auto-created from every email and ticket submission whether or not the team wants the CRM clutter g2.com β†—
Capterra reviewers cite limited customization on free/Starter tiers, with advanced reporting, custom objects, and ticket pipelines gated to Professional and Enterprise (~$100-$150/seat/month) capterra.com β†—
Independent comparisons recommend avoiding Service Hub if you don't already use HubSpot CRM, need enterprise-scale ticketing with deep routing/SLA management, want messaging-first support, or need a true free/low-cost option featurebase.app β†—
Software Advice reviews note knowledge base authoring and customer portal customization feel underpowered compared to Zendesk Guide or Intercom Articles softwareadvice.com β†—