What This Update Actually Is
HubSpot shipped a read-only public API endpoint for Conversation Recaps. It's currently in private beta with a September 2026 target release path.
The endpoint is: GET /notetaker/2026-09-beta/conversation/recap/{objectTypeId}/{objectId}. You pass in two path parameters: the CRM object type and the object ID. The response comes back with the AI-generated summary and the list of follow-up action items HubSpot produced for that recorded meeting.
Authorization requires the crm.objects.contacts.read scope. That keeps the access footprint narrow. It's read-only, so no write operations are included in this release.
One important caveat: the meeting must have a transcript. No transcript, no recap. If you're not consistently recording and transcribing calls, this API won't have data to return.
Why HubSpot Shipped This
Here's the real problem this solves. Your reps finish a call. HubSpot's AI writes a clean summary with action items. Then what happens?
In most portals we've audited, that intelligence sits inside HubSpot and goes no further. Humans who work outside the CRM, like engineers checking a project management tool or operations leaders reviewing a data warehouse, never see it. Someone has to log in, find the record, open the recap, copy it, and paste it somewhere else. That's manual work nobody wants to do.
The internal frustration is real too. RevOps teams building custom post-call workflows have had no clean way to fetch this data programmatically. They were either scraping the UI or asking reps to manually push summaries. Neither option scales.
HubSpot is betting that its AI-generated post-call intelligence is valuable enough that teams will want it everywhere, not just inside the CRM. This API is the bridge.
How to Use It Step by Step
- Confirm your subscription tier. This endpoint is available on Sales Hub Professional, Sales Hub Enterprise, Service Hub Professional, and Service Hub Enterprise. If you're on Starter, you don't have access yet.
- Request private beta access. As of the July 31, 2026 update date, this is still a private beta. Visit HubSpot's developer documentation and apply for beta access through the standard private beta request process.
- Set up your app with the correct OAuth scope. Your connected app must be authorized with the crm.objects.contacts.read scope. Verify this in your app settings under Private App scopes or OAuth configuration.
- Identify the objectTypeId and objectId for the CRM record tied to the meeting. For a contact, objectTypeId is 0-1. For a deal, it's 0-3. Check HubSpot's object type reference in the developer docs for the full list.
- Make the GET request. Call GET /notetaker/2026-09-beta/conversation/recap/{objectTypeId}/{objectId} with your bearer token. The response will include the AI summary and the action items array.
- Parse and route the data. Map the summary and action items into your target system, whether that's Slack, a Notion doc, a BI dashboard, a custom app, or an automation workflow you've already built.
- Handle the edge cases. Build error handling for records with no transcript, since those will return no recap data. Also plan for rate limits in line with HubSpot's standard API policies.
What It Touches in Your HubSpot Strategy
This isn't just a developer convenience. It changes how post-call intelligence flows across your entire revenue operation.
On the sales side, reps using the Sales Workspace get AI recaps today inside HubSpot. But your deal desk, your sales engineer, or your proposal team might live in a different tool. Now you can push that recap to wherever those humans actually work, right after the call ends.
On the service side, this pairs naturally with how teams are thinking about customer intelligence. If you've been exploring how HubSpot scores customer interactions, this API gives you the raw summary layer underneath that data so you can bring it into your own scoring models or dashboards.
For teams already working with HubSpot's CX Score for ticket intelligence, the Conversation Recap API is a natural companion. CX Score tells you how the interaction went. The recap tells you what was said and what happens next. Together they give you a complete post-call picture you can pipe anywhere.
Key Takeaway
If your team records calls with HubSpot's Notetaker, every one of those recaps is now available programmatically. You don't need to build a transcript parser or a summary model. HubSpot's AI already did that work. The API just unlocks the door.
From a RevOps architecture perspective, think about what this enables in your data pipelines. You can now enrich deal records in your data warehouse with call summaries. You can trigger downstream automations based on action items. You can feed post-call context into onboarding systems when a deal closes.
This also fits into the bigger picture of where HubSpot is heading with its AI platform. If you want the full context on how Breeze and agentic capabilities are evolving, the HubSpot Agentic Platform guide explains where the AI layer is heading and why APIs like this one are foundational to that vision.
Key Takeaway
The private beta status means early adopters get first-mover advantage. Teams that integrate this now will have post-call intelligence flowing into their custom tools before most competitors even know the API exists.
One limitation worth naming clearly: this is read-only. You can't push external summaries back into HubSpot through this endpoint. You also can't modify or delete recaps. If write access is on your roadmap, watch for future API versions.
Who Should Care Most
This update is primarily for technical humans building on top of HubSpot. But the business decision to pursue it starts with the right leaders.
- RevOps leaders who want post-call intelligence in their BI tools or data warehouse without manual exports.
- Sales ops managers running Sales Hub Pro or Enterprise who want to automate post-call follow-up triggers in external project management or task tools.
- Service ops managers on Service Hub Pro or Enterprise building custom dashboards that surface call context alongside ticket data.
- Developers and HubSpot partners building integrations where post-call context needs to flow into a custom app, a Slack bot, or a handoff workflow.
- Growing companies (50 to 500 employees) where sales and service teams record most calls but lack the technical infrastructure to use that data outside HubSpot.
If your organization doesn't record calls yet or doesn't use HubSpot's Notetaker to generate transcripts, this API won't deliver value. Get the recording and transcription workflow in place first.
George's Take
I've walked through a lot of portals where HubSpot's Notetaker is on, the AI is generating clean summaries after every call, and those summaries just sit there. Nobody's using them beyond the rep who occasionally glances at the recap before their next meeting. That's a waste of something genuinely good. When HubSpot's AI tells you what a prospect said they need and what you promised to do next, that information should be moving, not sitting idle in a timeline. This API is the right move because it lets teams decide where that intelligence lives and how it flows, instead of being stuck inside a UI that not everyone on the revenue team opens every day.
“HubSpot's AI is already doing the hard work of summarizing your calls. The Conversation Recap API finally lets that intelligence go where your humans actually work.”
Paired with other recent Sales Hub improvements like booking meetings directly from the Sales Workspace, the pattern is clear: HubSpot is building a tighter sales motion inside the CRM and then opening APIs so teams can extend that motion into any tool they choose. That's the right architecture.
If you're on Sales Hub or Service Hub Professional or Enterprise and you want to talk through how the Conversation Recap API fits into your current RevOps architecture, let's map it out together. Book a strategy call with the Sidekick team and we'll show you exactly where this fits in your portal and what to build first.
Frequently Asked Questions
What is the HubSpot Conversation Recap API?
The HubSpot Conversation Recap API is a read-only GET endpoint that lets developers programmatically retrieve AI-generated summaries and action items from any recorded meeting with a transcript. It's available in private beta as of July 2026 for Sales Hub and Service Hub Professional and Enterprise users.
Which HubSpot plans include the Conversation Recap API?
The Conversation Recap API is available on Sales Hub Professional, Sales Hub Enterprise, Service Hub Professional, and Service Hub Enterprise. Starter-tier users don't have access to this endpoint.
What OAuth scope does the Conversation Recap API require?
Apps using the Conversation Recap API must be authorized with the crm.objects.contacts.read scope. This keeps the access footprint minimal. No write scopes are required because the endpoint is read-only and doesn't allow modifying or creating recap data.
Does the Conversation Recap API work for all meetings in HubSpot?
No. The API only returns data for recorded meetings that have a transcript. If a meeting wasn't recorded or didn't produce a transcript through HubSpot's Notetaker, the endpoint won't return a recap. Teams should ensure consistent call recording and transcription before building against this API.
What data does the Conversation Recap API return?
The API returns two key pieces of data: the AI-generated conversation summary and the list of follow-up action items HubSpot produced for that meeting. It accepts the CRM object type ID and object ID as path parameters to identify which meeting's recap to retrieve.
How is the Conversation Recap API different from just reading the HubSpot UI?
The API lets developers pull post-call intelligence directly into external apps, data pipelines, Slack bots, dashboards, or automation workflows without anyone logging into HubSpot. It eliminates manual copy-paste and enables real-time post-call data flows that the HubSpot UI alone can't support.
