I'm learning what it is · 6 min read

What the Developer Platform pillar is, and what changed in 2026

You use HubSpot's API, webhooks, connectors or the marketplace, or you're deciding whether to build on top of the portal at all, and you want the developer-surface story without the admin-screen noise mixed in.

If you have five minutes

  • The Developer Platform tag inside HubSpot's own update feed catches three different kinds of thing at once: what you build on (the API, webhooks, connectors, agent tooling, the marketplace), what an admin configures (user import, access requests, passkey login, copying permissions between users), and what a reporting screen looks like (dashboard color themes, pivot-table column freezing).
  • This door is about the first one only.
1 of 4

If you came here looking for account settings, you're one door off

The Developer Platform tag inside HubSpot's own update feed catches three different kinds of thing at once: what you build on (the API, webhooks, connectors, agent tooling, the marketplace), what an admin configures (user import, access requests, passkey login, copying permissions between users), and what a reporting screen looks like (dashboard color themes, pivot-table column freezing). This door is about the first one only. If you clicked through hoping to sort out a permission set or a dashboard theme, that's a settings question every Hub shares — it isn't what makes this pillar its own thing.

What makes it its own thing is a single question worth asking about anything on this page: what happens when this runs and nobody's watching it. An API call, a webhook, an agent with tool access, a connector reading your CRM from inside another product — none of them wait for a human to click "confirm." The 2026 record on this pillar is mostly the story of HubSpot deciding what has to be true before that's safe.

2 of 4

The six pieces worth knowing, in one screen

  • Connectors and remote MCP — HubSpot's own connectors for Claude, Gemini and ChatGPT, plus Remote MCP Connectivity for HubSpot Agents (public beta, first covered 2026-07-29), are how an outside AI product reaches into a live portal and acts on what it finds there.
  • The API surface — the Contracts API (public beta, first covered 2026-08-04, shared with two other Hubs), the Payments Account Public READ API (live, 2026-08-03), the public API for CRM Pipeline Rules (public beta, first covered 2026-07-22), and the Account Info API's new fields for account name and creation date (live) are the pieces an integration calls directly rather than reading through a screen.
  • Agent tooling — Use Webhooks in custom agents (private beta, first covered 2026-07-20) lets an agent you build send a webhook as one of its tools. Describe an app, deploy it to your portal (private beta, first covered 2026-07-17) goes further: describe a page in plain language and it deploys as a real app inside your portal, reading live CRM data under your own permissions.
  • UI Extensions — FileUpload and FileViewer for UI Extensions (public beta, first covered 2026-06-24) closes a gap for anyone building a custom card that needs to hold files inside a record's own experience, instead of sending the user somewhere else.
  • The marketplace — a 193-app quarterly refresh (live, 2026-07-31), Improvements to Marketplace Submission Eligibility (live, 2026-08-19), and a redesigned Connected Apps overview and app-owner management screen (live) are the ecosystem side: what gets published, who can publish it, and who's accountable for an app once it's installed.
  • Deprecations and sunsets — the Pipelines API v1 deprecation and the Legacy Private App Creation sunset (both upcoming, no covered date recorded yet) are the two places HubSpot has told builders a path is closing, not opening.
3 of 4

What changed in 2026, in the order it shipped

  • 2026-06-24 — FileUpload and FileViewer for UI Extensions ships in public beta.
  • 2026-07-15 — the Rendering Locale Dataset Upgrade moves HubSpot's date, time, number and currency formatting from JRE to CLDR, the industry-standard dataset. Live, not a beta, and mostly invisible — Zach Hussion's take on it: "For most portals nothing changes. The people who should spot-check are the ones doing real development work." If your integration or your HubL depends on an exact formatted string, this is the one to check; if it doesn't, HubSpot describes it as a free accuracy upgrade you don't have to touch.
  • 2026-07-17 — Describe an app, deploy it to your portal ships in private beta and gets its own extended live build on the show. Chris Carolan's take: "For anyone already building apps outside HubSpot, there is now an infrastructure to build them directly into HubSpot instead."
  • 2026-07-20 — Use Webhooks in custom agents ships in private beta, the same week HubSpot started metering custom-agent runs against credits. Chris's take names the timing directly: "A capability expansion and a pricing change landing in the same week is not a coincidence."
  • 2026-07-22 — the public API for CRM Pipeline Rules ships in public beta.
  • 2026-07-29 — Remote MCP Connectivity for HubSpot Agents ships in public beta. No on-air take is recorded for this one yet.
  • 2026-07-31 — the marketplace's quarterly refresh lands: 193 new and 13 featured updated apps, live. Casey Hawkins and Chris Carolan's take covers two different stories in the same update — a client-side one about a sales team asking Breeze Assistant what a person had done recently and drafting from there, from inside Slack where they already live, and a structural one about HubSpot's own agent for Microsoft 365 Copilot: "But stuff like this is probably going to make it so a lot of integration building just starts to melt away."
  • 2026-08-03 — the Payments Account Public READ API ships, live.
  • 2026-08-04 — the Contracts API ships in public beta, shared with Revenue Hub and Sales Hub.
  • 2026-08-19 — Improvements to Marketplace Submission Eligibility ship, live, moving the bar for a new app's first listing from total installs to active installs.
  • 2026-08-21 — Primary ID Preservation for Merged Records ships in public beta. HubSpot's own record URL had always redirected the old ID to the survivor, so the underlying ID change stayed invisible until an integration depended on it. Chris's take on how he found it: "It wasn't until just really like less than a month ago that I did a merge using Claude through the MCP and Claude actually was like, just a heads up. Now these records have different IDs. And I was like, I'm sorry, what?"
  • No covered date recorded yet for: Connected Apps' redesigned overview and app-owner management, HubSpot Connector for Gemini, updates to the HubSpot connector for ChatGPT, updates to the HubSpot connector for Claude and remote MCP server, the Pipelines API v1 deprecation, the Legacy Private App Creation sunset, the Account Info API's account-name and creation-date fields, and Location as Restriction (making a card's location optional) — each one is a member of this pillar and each one is live or upcoming per HubSpot's own status field, but none has an episode association in the archive yet, so there's no on-air take to quote.
4 of 4

The pattern under the year

Read the eight updates above that did earn a take, and none of the biggest reactions were about a new capability by itself. They were about what has to be true before HubSpot hands more reach to something that runs unattended. A merge that quietly changes a record's ID is fine until an integration is built on the assumption it never will — which is exactly why Primary ID Preservation got tagged a major update. An outside system that has to guess whether a payments account is ready is fine until the guess is wrong at 2am — which is exactly the case the Payments Account READ API removes. And an agent that can now send a webhook is fine right up until nobody notices the same week HubSpot started charging for every time an agent runs — which is why the take on webhooks named the coincidence instead of ignoring it.

What this pillar is actually tracking

Not "what can you build" — that's been true for years. What's changing in 2026 is what HubSpot is willing to let something build without a person watching it happen, and what it ships alongside that reach to make it survivable: a stable ID, a state you can check instead of assume, a metered cost instead of an unlimited one.

"For most portals nothing changes. The people who should spot-check are the ones doing real development work." — Zach Hussion, Rendering Locale Dataset Upgrade: JRE to CLDR.

"It wasn't until just really like less than a month ago that I did a merge using Claude through the MCP and Claude actually was like, just a heads up. Now these records have different IDs. And I was like, I'm sorry, what?" — Chris Carolan, Primary ID Preservation for Merged Records.

Where to next

Where this comes from

  • The show's own update pages. every quote here is the take published at anotherorangemorning.com/hubspot-updates/{slug}, curled live and checked line by line on 2026-09-05
  • The live HubSpot Updates read, 2026-09-05. every status and first-covered date is the value on the update's own record at the time of that read, calibrated against a known-nonzero control before it was trusted
  • The Sanity episode archive across every show, read 2026-09-05. the back-catalog pointers were matched on title, description and keyTopics; no episode was read past its own metadata, and this page says so where it uses them
  • Chris's steer on this pillar, the nine-Hub walk, 2026-09-05. "Shouldn't this Hub focus on API related updates?" — read as the developer surface, with the admin, account and reporting-UI records filed under the same value treated as tagging debt rather than members

What we do not know yet

  • The AOM back catalog is deep on this pillar's own updates — every member update above with an on-air take was covered at length, several with a dedicated segment — but the wider media archive is thin on dedicated coverage of this Hub specifically, unlike Revenue Hub's back catalog. What exists is real but scattered:
  • The show covered HubSpot's own Staff Product Manager unboxing the HubSpot MCP server on 2025-10-21 (Let's Build AI Skills Daily).
  • The show covered a HubSpot connector (Box) unboxing with the integration's own CEO on 2024-12-12 (Let's Build HubSpot Apps), and a different HubSpot connector (Orderwise) unboxing with its builder on 2025-06-18 (Let's Unbox).
  • The show covered HubSpot's Sandbox beta, a developer/admin-environment feature, on 2025-06-06 (Let's Build HubSpot Super Admins).
  • The show covered someone building and launching a HubSpot Marketplace app solo, as one of several topics, on 2026-08-19 (The Road to UNBOUND).
  • The show covered HubSpot's Breeze vibe-coding private beta — the same capability as Describe an app, deploy it to your portal — on 2026-07-21 (Value-First AI Daily), and the HubSpot Price Books API on 2026-07-27 (Value-First AI Daily).
  • The show covered a HubSpot MCP server, remote edition, for AI connectors on 2026-01-27 (Value-First AI Daily).
  • The Contracts API specifically — shared with Revenue Hub — has its own dedicated coverage there: HubSpot's Director of Product Management for Billing and Revenue Hub was a guest on 2026-09-03 (Let's Unbox).
  • None of the above was read past its title, description and keyTopics for this door — they're pointers to where the show has already gone, not summaries of what was said. If you're deciding whether to build against remote MCP, a connector, or the marketplace, those episodes are the place to start watching before you start building.