What This Update Actually Is
HubSpot shipped a public API for Sales Templates. That means developers can now interact with sales email templates in HubSpot from outside the portal, using standard API calls.
The API supports five core actions:
- Get a list of templates so you can pull your full template library into an external system
- Get a list of folders so you can map your template organization structure
- Create a new template so you can push content from external tools directly into HubSpot
- Get a specific template so you can read individual template data for auditing or syncing
- Update a specific template so you can push revisions without logging into HubSpot manually
One important caveat: these endpoints require user-level app permissions. If your existing app uses portal-level access, it won't work with this API without a rebuild. That's not a footnote; it's a hard blocker worth flagging before your developer spends an afternoon wondering why the calls are failing.
Why HubSpot Shipped This
Before this API existed, sales templates lived in a walled garden inside HubSpot. If your team managed messaging in a content governance tool, a Git repo, or a custom internal system, there was no clean bridge. Someone had to copy-paste.
That copy-paste tax compounds fast. Templates drift from brand standards. Reps use outdated messaging because nobody noticed the update didn't get synced. RevOps leaders lose visibility into what's actually in the portal.
This API closes that loop. External tools can now read, create, and update templates in HubSpot directly. The portal becomes the source of truth, not a destination that's always slightly out of date.
How to Use It Step by Step
This is a developer-facing API, so the setup lives in code, not in the portal UI. Here's the practical path to getting it working:
- Review the HubSpot API documentation for the Sales Templates endpoints. The docs cover the full request and response shapes for all five supported actions.
- Confirm your app uses user-level access. If it currently uses portal-level access, you'll need to rebuild it with the correct permission scope before any of these endpoints will respond. This is the single most important step to check first.
- Authenticate with user-level OAuth scopes. Make sure your integration flow prompts for the correct user context, not just portal-level credentials.
- Call the list templates endpoint first. Use the response to map your existing template library before building any create or update logic.
- Build your sync logic. Whether you're pushing from a CMS, a content governance platform, or a custom internal tool, use the create and update endpoints to keep HubSpot current without manual intervention.
- Test in a sandbox or staging account before pushing to production. Because this API writes to the templates your reps actually use, a bad update can affect live outreach immediately.
What It Touches in Your HubSpot Strategy
This update is narrowly scoped in what it does, but broadly meaningful in what it enables. Here's where it ripples.
Sales Hub is the direct home. Templates live in Sales Hub, and all five API actions operate on Sales Hub template objects. Every tier from Free to Enterprise gets access.
RevOps and content governance workflows are the bigger win. If your organization maintains messaging standards in a central repository, a design system, or a brand governance tool, this API lets those systems become the source that populates HubSpot. No more manual sync steps. No more "did someone update the HubSpot version?" on a Monday morning.
Key Takeaway
If your sales team sends email through HubSpot but your messaging is owned by marketing or a content team outside the portal, this API is the bridge you've been missing. It lets the right humans own the words without needing portal access to push them.
Integrations with external CRM, enablement, or content tools are now cleaner. Tools like Seismic, Highspot, or custom internal content hubs can push finalized templates into HubSpot without a human in the middle. That's a meaningful reduction in time-to-rep for new messaging.
Portal auditing gets easier. The get-list and get-specific endpoints let you pull template data for auditing outside the portal. If you've ever tried to do a comprehensive HubSpot portal audit and wished you could export template metadata cleanly, this API is the start of that answer.
This update pairs naturally with the Contracts API HubSpot released earlier in 2026. Both APIs move HubSpot sales content out of the UI and into programmatic reach. If your team is building a sales content automation layer on top of HubSpot, these two belong in the same architecture conversation.
Key Takeaway
The user-level access requirement is a real constraint. Any existing app built with portal-level access won't work here without a rebuild. Audit your current app permissions before planning a rollout timeline.
Who Should Care Most
Not every HubSpot update is for everyone. Here's who should move on this one:
- RevOps leaders managing large template libraries who need a reliable way to keep HubSpot in sync with messaging that's owned and updated elsewhere
- HubSpot developers and integration architects building connectors between HubSpot and sales enablement tools, content management systems, or custom internal platforms
- Sales enablement managers at companies where marketing writes the templates but reps use them in HubSpot, and the current hand-off process involves copy-paste or tickets
- Agencies managing HubSpot portals for multiple clients who want to automate template deployment across accounts without logging into each one manually
- Companies on any Sales Hub tier, including Free, since this API is available across all four tiers
If your portal has fewer than a dozen templates and one person manages them directly in HubSpot, this isn't urgent for you. But if you're at scale or building toward it, it's worth understanding now.
George's Take
What I keep seeing in portals is a gap between who owns the messaging and who can actually put it in front of reps. Marketing writes brilliant templates in a Google Doc or a content system, and then someone, usually the most overloaded person on the RevOps team, has to manually paste it into HubSpot. That's not a process; that's a liability. This API doesn't just save time. It closes an accountability gap. When the external system is authoritative and HubSpot stays in sync automatically, the humans who own the words can actually own the outcome too. That's the shift worth paying attention to here.
“When the system that owns your messaging and the system your reps use every day are finally talking to each other, you stop losing deals to outdated copy. That's not a small thing.”
If you're wondering how this fits into a broader sales enablement or RevOps architecture, check out what we've shared on the Leads card in the HubSpot Sales Extension sidebar for context on how HubSpot is systematically expanding the programmatic and in-context reach of sales tooling in 2026.
If you want help thinking through how the Sales Templates API fits into your HubSpot architecture, or whether your current app setup even supports user-level access, let's talk. Book a strategy call with the Sidekick team and we'll map it out with you.
Frequently Asked Questions
What is the HubSpot Sales Templates Public API?
It's a new HubSpot API that lets developers programmatically get, create, and update sales email templates and folders from external tools. It's available in public beta starting September 6, 2026, across all Sales Hub tiers including Free. It requires user-level app permissions to function.
Which HubSpot plans include the Sales Templates API?
The Sales Templates Public API is available on all Sales Hub tiers: Free, Starter, Professional, and Enterprise. There's no tier restriction on access, which makes it one of the broader API releases HubSpot has shipped in the sales tooling space.
What's the difference between user-level and portal-level app access in HubSpot?
Portal-level access grants API permissions at the account level without tying actions to a specific user. User-level access requires the app to act on behalf of a specific authenticated user. The Sales Templates API requires user-level access, so existing apps built with portal-level access won't work with these endpoints without a rebuild.
Can the Sales Templates API push templates from external tools into HubSpot?
Yes. The create template endpoint lets external systems push new templates directly into HubSpot. The update endpoint lets you revise existing templates without logging into the portal. This makes it possible to manage templates in a source-of-truth system and keep HubSpot automatically current.
Does the Sales Templates API work with Sales Hub Free?
Yes. HubSpot has made this API available to all Sales Hub tiers, including Free. Any account on Sales Free, Starter, Professional, or Enterprise can use these endpoints, provided the app making the calls uses user-level OAuth access rather than portal-level access.
What can developers do with the Sales Templates API right now?
As of the September 2026 release, developers can list all templates, list all folders, get a specific template by ID, create a new template, and update an existing template. Delete and folder management endpoints are not listed in the current release scope, so check HubSpot's API docs for the latest.
