HubSpot for Developers

The April HubSpot Developer Newsletter has dropped 🤩 Highlights: Spring Spotlight 2026 brought some of the biggest platform changes of the year and both the local + remote HubSpot MCP servers graduated from beta. Date-based API versioning is generally available and the Developer Platform 2026.03 ships with serverless functions back in the Projects framework. Also in this issue: → New Build & Ship a HubSpot App YouTube series → Dev Platform Playground returns June 3 → Legacy public app creation sunset starting May 26 → Five migration deadlines between now and October starting with v1 Lists API sunset April 30 👇 Read the full newsletter below 👇

Three years ago, our engineering team started adopting generative AI like everyone else. Copilots. Code completion. The usual starting point. But when those tools hit their ceiling, we didn't just go looking for better ones. We built the foundation underneath them. That decision compounded faster than we expected. Today, 100% of our engineers use AI tools and lines of code per engineer are up 73%. But honestly, the productivity numbers aren't the point. The point is that we can now ship better products, faster, and our customers feel that difference. Yamini Rangan just wrote about the full journey, detailing three phases, real infrastructure investment, and a willingness to build what didn't exist yet. If you're thinking through how your engineering team builds with AI, there's a lot here worth reading. https://lnkd.in/g8gkpGnN

We're hosting an event for NY TECH WEEK by a16z! It's called Build Mode. Wednesday, June 3, in NYC. The premise: your CRM isn't a database, it's a platform. RevOps leads, GTM operators, and founders are already shipping on it: custom workflows that save hours a week, lead gen apps, internal tools that quietly replaced five-figure SaaS contracts. If you've built something on HubSpot you're proud of, this is your room - and, if you want to share what you've built as either a panelist or in a demo - get in touch! Wed, June 3, 6–8 PM ET NYC venue TBD RSVP at the link in the comments! More details are coming soon. Hosted by HubSpot for Developers 🧡 #HubSpotDevelopers #NYTechWee

Hey all! Starting May 26th, 2026, you’ll no longer be able to create new #HubSpot legacy public apps in the UI. New public apps should instead be built using our project-based platform. Timeline: - New accounts: May 26, 2026 - Existing accounts: June 23, 2026 Existing legacy public apps aren’t affected and will continue to run as-is. If you’re building for the Marketplace, now’s a good time to start using HubSpot for Developers Projects since it supports CLI workflows, UI extensions, and easier deployments. 🔗 Learn more: https://lnkd.in/erkxCW32 🔗 Join the discussion: https://lnkd.in/e3aGtE_P #HubSpotDevelopers #ProductUpdate

HubSpot 𝗷𝘂𝘀𝘁 𝗱𝗿𝗼𝗽𝗽𝗲𝗱 𝗼𝗻𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝘂𝗽𝗱𝗮𝘁𝗲𝘀 𝗼𝗳 𝟮𝟬𝟮𝟲. And almost nobody noticed. Buried in the beta release: AI agents can now 𝗖𝗥𝗘𝗔𝗧𝗘 workflows in HubSpot. Not trigger them. Not edit them. Not read them. 𝗖𝗿𝗲𝗮𝘁𝗲 𝘁𝗵𝗲𝗺. 𝗙𝗿𝗼𝗺 𝘀𝗰𝗿𝗮𝘁𝗰𝗵. For years, HubSpot's API let AI do almost everything inside your portal read records, push data, fire automations. The one missing piece was always: building the actual workflow. That part required a human in the workflow builder. That part just shipped. So what does this actually unlock? Picture asking your AI assistant: "Build me a workflow that re-engages contacts who opened our last 3 emails but never clicked." And it just… does it. Logic, branches, delays, internal notifications, properties all built. You review it, approve it, turn it on. A few wild things this makes possible: → Self-healing portals that detect broken automations and rebuild them → Onboarding bots that spin up a new customer's full workflow stack in minutes → Playbook engines that ship a new sequence the second a new ICP is spotted → Workflows that A/B test themselves and quietly ship the winner This is the moment HubSpot stops being a CRM with AI features… And starts becoming a platform that AI can actually operate inside. Massive unlock. What's the first workflow you'd want an AI to build for you in HubSpot?

HubSpot Spring Spotlight is here 👀 and it's all about the context advantage. The big updates are centered around 3 goals: Build Awareness (marketing), Grow Revenue (sales), and Scale Support (service). It doesn't matter how long you've been using HubSpot, in fact I'd argue that the longer you've been using it, the more important it is that you dive into these use cases and get your hands on the updated tools. My favorite feature of the website is the "All Updates" section, where you can filter updates by goal or by HubSpot products. This is a great way to find the updates most important to you, it also makes quick work of skimming the updates. A few you can't miss: ✨ HubSpot AEO (Answer Engine Optimization) now in public beta, forget everything you've heard about it because this was rebuilt from the ground up by the team at XFunnel (Acquired by HubSpot) ✨ HubSpot AI Connectors the big 4 are here, now you can bring HubSpot data into ChatGPT, Gemini, Claude, and Copilot so it works where you do. ✨ Serverless Functions are back in 2026.3 with expanded support for UI extensions, including App Settings and App Homes, and can be executed in test accounts (requires Enterprise subscription in non-test accounts) Make sure you're following the HubSpot for Developers team to catch all of the Developer Platform updates, I'll drop the link all of the developer updates in the comments. Go check it out and come back to let me know what you're most excited about!

🔥 1 BIG problem devs have when addressing 429 errors (HubSpot rate limits!). Adopting Batch Read APIs to batch up to 100 records is a smart move, however... it needs to be implemented correctly to handle [207] replies!! Data not getting sync'd is a top 3 customer concern and apps that treat any non-4xx 5xx status as a full success are contributing to this by silently discard failed records. Batch read endpoints return [207] Multi-Status when some records in the request were retrieved successfully and others were not. Here is the correct implementation: - Always inspect the full response body on every batch read call, regardless of HTTP status code. - The response body contains two arrays: results (successfully retrieved records) and errors (failed records with individual error codes and the IDs that caused the failure). Process results normally. Do not discard errors. - For each entry in errors, extract the object ID and the specific error code. A [404] within the errors array means that ID no longer exists in the portal — remove it from local sync state and do not retry it. Any other error code should be logged and retried individually. - Do not retry the full original batch after a [207]. Only retry the failed IDs, individually or in a corrective batch, after resolving the underlying cause. Finally, maintain a local registry of IDs that have previously appeared in [207] error arrays. IDs that fail repeatedly across multiple batch reads are permanently stale and should be purged from sync state entirely rather than carried forward indefinitely. A persistently high [207] rate on batch read endpoints — visible in telemetry as a large share of calls returning 207 — is a signal that stale IDs are accumulating faster than they are being purged. The underlying cause is almost always that the integration is not subscribed to HubSpot object deletion and merge webhooks, so it has no mechanism to invalidate stored IDs when records are removed. Subscribing to those events and triggering immediate ID invalidation is the durable fix. Batch read hygiene handles the cleanup; webhook subscriptions prevent the accumulation. #HubSpot HubSpot for Developers Steve Laham Sarah Jane (SJ) Morris Jennifer Nixon Daniel Jacobson Cody Holden Rachel Kellam Isaac Takushi Karen Ng

Spring Spotlight 2026 is live ✨ What's new for the HubSpot Developer Platform: → Date-based versioned APIs and versioned developer docs → HubSpot Projects v2026.03 with serverless functions → MCP servers (remote + local) for AI-powered development → Service Keys that simplify auth without building a full app → App Pages with UI Extensions for full-page in-app experiences → Searchable CRM object definitions now in beta We built this one around stability and speed so you can ship with confidence. Explore the full developer roundup: https://bit.ly/4tOJeFy

Wow, what a week it’s been! If you’ve seen the recent update about HubSpot for Developers’ new date-based API versioning for developers… trust me, you’re not dreaming. This launch has truly been a team effort—bringing together a huge amount of dedication, strategy, and collaboration across multiple teams. There were plenty of late nights and early mornings, but it’s been amazing to see it all come together. Even more exciting: this new versioning framework is a big step forward for HubSpot’s developer platform and the tools that support it. Keep an eye out for more on that during Spring Spotlight 👀 In the meantime, I’m excited to share a blog post that breaks down what this all means: https://lnkd.in/eUCjQsCC This was all made possible by the hard work of so many people involved: Huge shoutout to Rachel Kellam, John Whalen, Walker Christie, Rohit Panicker, Farheen M., Edward Langan, David Adams, Joe K., Jon McLaren, Jackie Valenzuela, Sejal Parikh, Chris Riley, Eric Devenney, Seth Kaplan, Eleonora Ludin, Cody Holden, and the team behind the SDKs (and many others!). This truly took a village. Quick note: Postman collections for the DBV APIs are actively in progress. Rohit Panicker and I are also working with Postman on a more automated approach so future updates are faster and more seamless—stay tuned!

At Dev Playground a few weeks ago with HubSpot for Developers, the HubSpot developer community came with great questions: sign-on scenarios, exemption edge cases, how to opt in, and whether Seamless Install makes sense for your business. So we put it all on tape. 📹 The HubSpot Developer Channel now has the full demo series: → Why Seamless Install matters for your business → How to opt in → Install flow without partner sign-on → Install flow with partner sign-on → Exemption flow Missed the session, or just want a reference you can come back to? Full YouTube playlist here: https://lnkd.in/eK4rXWhM Special thanks to Harish Srinivasan, Dennis Edson, Eileen C. and Ricky Diep for the collab on this one.