What This Update Actually Is
HubSpot quietly added two new optional fields to its Account Info API endpoint at /v3/details: portalName and createdAt.
portalName returns the human-readable name of the HubSpot account. createdAt returns the account creation timestamp as a Unix value in milliseconds. Both fields are optional, so if an account has no name set, the field simply won't appear in the response.
Existing integrations aren't affected at all. Prior API versions stay exactly as they were. There's no change to the HubSpot interface itself. This is a pure API addition for developers and the tools they build.
Why HubSpot Shipped This
Here's the real problem. As more teams connect HubSpot to external AI tools, like Claude, ChatGPT, or Breeze, humans often have no idea which HubSpot portal the AI is actually talking to. If you work across multiple accounts or manage portals for clients, that's not a minor annoyance. It's a real risk.
Before this update, the only way to confirm the connected account was to leave the chat, check a settings screen, and come back. For a fast-moving conversation where you're pulling pipeline data or running a CRM lookup, that context switch slows everything down.
We've seen this friction play out specifically with the Breeze Assistant in Claude connector, where operators juggling multiple portals have had to pause a conversation just to verify they're in the right account. Now the tool can answer that question itself, right inside the chat.
The createdAt field adds a second layer of confirmation. Two portals might share a similar name. The creation date gives tools a way to disambiguate and give humans a precise, verifiable answer.
How to Use It Step by Step
This update is developer-facing, so the steps below apply to anyone building or maintaining a tool on the HubSpot API. If you're using a managed connector like the Breeze Assistant or a third-party AI integration, the connector's developer would handle this on your behalf.
- Upgrade to the latest version of the Account Info API so your calls hit /v3/details and not a legacy endpoint.
- Make a GET request to /account-info/v3/details using your existing credentials. No new scopes are required.
- Check the response for portalName and createdAt. Remember: both are optional. Code defensively so your tool doesn't break if an account has no name set.
- Parse createdAt as a Unix timestamp in milliseconds. Convert it to a readable date format before surfacing it to humans inside a chat interface.
- Build a simple confirmation response into your AI connector, something like: "You're connected to [portalName], created on [date]." Show it when a user asks which account the tool is accessing.
- Leave your existing integrations alone. Prior API versions are unchanged, so nothing breaks if you haven't yet migrated to v3.
What It Touches in Your HubSpot Strategy
On the surface, this looks like a small developer tweak. But it connects to a bigger pattern we're watching across HubSpot's API roadmap: giving AI tools enough context to operate confidently without interrupting the human in the conversation.
For revops teams managing multiple portals, whether for different brands, regions, or clients, account identity is foundational. Getting a wrong-account answer to a pipeline question isn't just confusing. It can lead to bad decisions based on the wrong data.
Key Takeaway
If your team works across more than one HubSpot portal, push your AI connector developers to implement portalName and createdAt immediately. It's a one-call fix that eliminates an entire category of account confusion errors.
This update also matters for the broader AI connector ecosystem. HubSpot now supports Breeze, Claude, and ChatGPT connectors natively. As those integrations deepen, account identity becomes a shared infrastructure requirement. This field is the foundation.
It also pairs well with recent credential infrastructure changes. If you're already working with HubSpot Account Service Keys to manage secure API access, adding portalName and createdAt to your response handling is a natural next step in building trustworthy, auditable AI integrations.
If you're newer to how Breeze operates at the API level, our breakdown of what HubSpot's Breeze Assistant can actually do gives you the strategic context for why account identity matters so much as these tools gain more autonomous capability.
Key Takeaway
This update doesn't change what AI connectors can do. It changes how reliably they can confirm where they're doing it. That's a meaningful difference when you're making decisions based on live CRM data.
Who Should Care Most
Not everyone needs to act on this right now. Here's who should pay attention.
- HubSpot developers and integration builders who maintain AI chat connectors and need to surface account context reliably for the humans using those tools.
- RevOps leaders managing multiple HubSpot portals, whether across clients, brands, or business units, where a wrong-account interaction could corrupt reporting or trigger the wrong workflow.
- HubSpot agency partners and solutions partners who build custom integrations for clients and need a reliable way to confirm account identity inside AI-assisted workflows.
- Operations-heavy companies running AI copilot tools inside sales and service teams, where humans asking the AI a question need to trust the context that answer is coming from.
If your team uses exactly one HubSpot portal and doesn't build custom integrations, you can safely skip this one. The Breeze connector you're using will handle it on the backend without any action from you.
George's Take
I know this one looks like a footnote in the release notes. Two optional API fields, no UI change, no fanfare. But here's what I keep coming back to: as AI tools take on more real work inside HubSpot, the question of "which account am I in?" becomes the same kind of question as "who is this contact?" or "what's the status of this deal?" It's foundational context. Without it, the AI is operating blind, and the humans trusting it are exposed. HubSpot building account identity directly into the API response is the right call, and I'm glad they shipped it for all tiers. The teams who'll benefit most aren't the big enterprises. They're the lean revops operators who use Claude or Breeze across a handful of portals and need every call to land in exactly the right place.
“Account identity isn't a developer nicety. It's the foundation that makes every AI-assisted HubSpot interaction trustworthy. Get this right and everything built on top of it gets safer.”
If your team uses HubSpot across multiple portals and you're starting to layer AI tools into your daily workflows, this is a good moment to audit how your integrations confirm account context. We can help you map that out. Book a strategy call with Sidekick and let's make sure your AI connectors are working on the right data, in the right portal, every time.
Frequently Asked Questions
What are the new fields in HubSpot's Account Info API?
HubSpot added portalName and createdAt to the /account-info/v3/details endpoint. portalName returns the readable name of the HubSpot account. createdAt returns the account creation date as a Unix timestamp in milliseconds. Both fields are optional and won't appear if the value isn't set for that account.
Which HubSpot AI connectors benefit from the portalName and createdAt fields?
Any tool built on the Account Info API can use these fields, including the native connectors for Claude, ChatGPT, and HubSpot Breeze. They allow those tools to confirm which HubSpot account they're connected to and display that information directly inside the conversation, without the user leaving the chat.
Does this update break existing HubSpot API integrations?
No. HubSpot kept all prior API versions unchanged. If your integration uses an older version of the Account Info API, it will continue to work exactly as before. The new portalName and createdAt fields are only available when you call /v3/details. No migration is required unless you want the new fields.
Is this update available on all HubSpot plans?
Yes. This API update is available to all HubSpot accounts across all hubs and tiers, including free accounts. There's no plan restriction. However, the update is developer-facing, so you'll need access to the Account Info API or a connector that implements it to take advantage of the new fields.
Why does createdAt use a Unix timestamp instead of a standard date format?
Unix timestamps in milliseconds are a common API standard because they're timezone-neutral and easy to convert programmatically. Your integration or connector is responsible for converting that number into a human-readable date before displaying it. Most modern languages and frameworks handle this conversion in one or two lines of code.
Does this update change anything in the HubSpot interface?
No. There is no change to the HubSpot UI from this update. It's entirely an API-level change. The portal name and creation date are now available to external tools and AI connectors that call the Account Info API, but nothing looks different inside your HubSpot account settings or dashboard.





