What This Update Actually Is
HubSpot expanded its existing Transcripts API to allow retrieval of any call or meeting transcript stored in the CRM. Before this update, third-party integrations could only access transcripts they created themselves. Now, any developer with a private app and account-level authentication can retrieve HubSpot-generated transcripts too.
The API returns the best available transcript for a given conversation across all supported transcript sources. That includes calls logged natively in HubSpot, meeting recordings, and notes. Retrieval happens immediately after the transcript is created, so there's no lag between the conversation ending and the data being available.
A few hard limits to know upfront: there's no dedicated bulk export endpoint or transcript-listing endpoint in this release. For high-volume scenarios, developers need to first query CRM APIs to find relevant call or meeting records, then retrieve each transcript individually. Also, the API does not currently support deleting HubSpot-generated recordings or transcripts.
Why HubSpot Shipped This
Conversation data has always been one of HubSpot's richest signals. But until now, that data was largely locked inside the portal. Humans building RevOps systems, coaching dashboards, or AI-powered analysis tools had no clean path to pull transcript text out programmatically.
The frustration is real. Sales teams generate dozens of calls a week. Service teams handle hundreds of conversations. All of that text sits in HubSpot while the analysis tools, data warehouses, and coaching platforms these teams rely on stay empty. This update removes that gap.
HubSpot's move here also reflects a broader platform shift. As more teams build agentic and AI-powered workflows on top of CRM data, raw conversation text becomes foundational input. You can't train a coaching model or run sentiment analysis on data you can't access. This API opens that door.
How to Use It Step by Step
Here's the practical path for a developer setting this up for the first time.
- Create a private app in HubSpot with the required CRM scopes. Account-level authentication via a private app is the supported method. Personal API keys won't work here.
- Use HubSpot's CRM APIs to query calls or meetings. Filter by date range, owner, or contact to find the engagement IDs you need. Each call or meeting in HubSpot has a unique engagement ID.
- Send a POST request to the Transcripts API endpoint at https://api.hubapi.com/crm/extensions/calling/2026-09/transcripts using your Bearer token. Include the engagementId in the request body.
- Parse the response. HubSpot returns the transcript as structured utterances, each with speaker ID, speaker name, speaker email, start time in milliseconds, end time in milliseconds, and text content. The languageCode field is also included per utterance.
- Route the structured data into your destination system. That might be a data warehouse, a coaching tool, a custom dashboard, or an AI pipeline. Because the data is structured per speaker and per utterance, it maps cleanly to most downstream schemas.
- Repeat per record for bulk workflows. There's no batch endpoint yet, so loop through each engagement ID individually. Plan your rate limit strategy accordingly using HubSpot's standard API call limits.
Full API reference is available in HubSpot's developer documentation at developers.hubspot.com. If your account has Sensitive Data or HIPAA features enabled, stop here: this expanded access isn't available for your account in this release.
What It Touches in Your HubSpot Strategy
This update isn't just a developer convenience. It ripples across how sales and service teams capture, analyze, and act on conversation intelligence.
On the Sales Hub side, call coaching workflows get a real upgrade. Managers who used to manually review calls can now route transcripts automatically into scoring tools or LLMs for pattern analysis. Objection tracking, talk ratio analysis, and competitive mention detection all become possible when transcript text flows freely.
On the Service Hub side, this connects directly to quality assurance. Teams running high-volume support conversations can now export transcripts for CSAT correlation, escalation pattern detection, or agent performance benchmarking outside HubSpot's native reporting.
Key Takeaway
The Transcripts API returns data as structured utterances with speaker identity, timestamps, and language code. This makes it directly compatible with most AI and analytics pipelines without custom pre-processing.
If your team is already using the CRM API layer for other automation work, this fits naturally into that stack. Similar to how the CRM Pipeline Object Tags API opened up programmatic tag management, this update continues HubSpot's pattern of exposing CRM data that previously required manual exports or screen-scraping workarounds.
For operations and RevOps leaders thinking about data architecture, this also matters for your API call budget. Retrieving transcripts at scale, record by record, will consume API calls. Review your current usage before building a high-volume pipeline. HubSpot's subscription limits page is a good place to check your headroom.
Key Takeaway
There's no bulk transcript endpoint in this release. For portals with thousands of calls per month, build a queue-based retrieval system and monitor your API call consumption carefully before going to production.
If you haven't already reviewed your portal's API consumption, our breakdown of HubSpot's subscription entitlements and usage limits will show you exactly where to look before you build.
Third-party integrations aren't disrupted here. Tools that already write transcripts to HubSpot via the API can still read their own transcripts exactly as before. The new expanded access adds on top, it doesn't change existing behavior.
Who Should Care Most
This update is most immediately useful for a specific set of roles and company types.
- RevOps and marketing ops leaders who are building conversation intelligence into their reporting stack and need transcript data flowing into a warehouse or BI tool.
- Sales enablement managers at companies with 15 or more reps who want to run automated call scoring or coaching analysis without listening to every recording manually.
- Service operations leads running high-volume support teams who need transcript data for QA scoring, escalation audits, or CSAT analysis outside of HubSpot.
- Developers and HubSpot partners building custom integrations, AI pipelines, or agentic workflows where conversation text is a core data input.
- Growing companies on Sales Hub or Service Hub Starter who want to use conversation data strategically without paying for expensive third-party conversation intelligence platforms.
If your account has Sensitive Data or HIPAA features enabled, this update doesn't apply to you yet. HubSpot hasn't announced a timeline for that expansion.
George's Take
We've worked inside hundreds of HubSpot portals, and the pattern is always the same: the humans generating the most valuable conversation data, your sales reps and service agents, never see it turned into anything actionable. Transcripts pile up. Managers skim a handful. Most of the signal just disappears. This API changes that calculus. Now you can build systems that actually read every conversation, score it, route it, and feed it back into the tools your teams already use. That's not a small thing. That's the difference between conversation data being a record and being a resource.
“Conversation data has always been HubSpot's best-kept secret. This API finally lets you do something with it beyond hoping someone has time to listen.”
If you're thinking about where this fits in a broader AI strategy for your portal, our guide to the HubSpot agentic platform will give you a fuller picture of how these data access APIs connect to the agentic workflows HubSpot is building toward.
If you want help designing an API integration that actually puts your transcript data to work, let's talk. Our team builds these systems for growing companies every day. Book a strategy call with Sidekick Strategies and we'll map out exactly what's possible for your portal.
Frequently Asked Questions
What is the HubSpot Transcripts API?
The HubSpot Transcripts API lets developers programmatically retrieve call and meeting transcripts stored in HubSpot. Using a private app for authentication, you can pull transcript text, speaker identity, timestamps, and language data for any call or meeting engagement and route it into external systems or analytics tools.
Which HubSpot plans include access to the Transcripts API?
The expanded Transcripts API access is available on Sales Hub Starter, Sales Hub Professional, Sales Hub Enterprise, Service Hub Starter, and Service Hub Professional. Accounts with Sensitive Data or HIPAA features enabled are not included in this initial release.
Can I bulk export all transcripts from HubSpot via the API?
Not in a single request. HubSpot hasn't released a dedicated bulk transcript export or transcript-listing endpoint in this update. For high-volume workflows, you need to query CRM APIs to find call and meeting engagement IDs first, then retrieve each transcript individually in a loop.
Can I delete HubSpot-generated transcripts using the Transcripts API?
No. As of this release, the expanded API access does not support deleting HubSpot-generated recordings or transcripts. Third-party integrations can still manage the transcripts they created themselves, but deletion of HubSpot-native transcripts via API isn't currently supported.
What authentication method does the HubSpot Transcripts API require?
The Transcripts API requires account-level authentication. HubSpot recommends using a private app with a Bearer token. Personal API keys are not a supported method for this endpoint.
Will existing third-party calling integrations be affected by this update?
No. Third-party integrations that already create transcripts and access their own transcript data will continue working exactly as before. This update adds expanded access for HubSpot-generated transcripts on top of existing behavior without changing how current integrations function.
