What This Update Actually Is
HubSpot is sunsetting the Pipelines API V1 on December 4, 2026. After that date, the endpoint is gone. It won't return errors gracefully. It simply won't respond.
The replacement is the 2026-09 version of the Pipelines API. That version is available now, it's documented, and it's what HubSpot is building on going forward.
The Pipelines API controls how your deal pipelines, ticket pipelines, and custom object pipelines are created, read, updated, and deleted programmatically. If any outside system touches your pipeline structure through code, this affects you.
Why HubSpot Shipped This
API versioning is how software platforms evolve without breaking everything at once. V1 was built years ago. It doesn't reflect how HubSpot's data model works today, and it limits what the product team can ship.
The 2026-09 version is aligned with HubSpot's current API architecture. That means better error handling, more consistent response shapes, and support for features that V1 simply can't carry.
Keeping V1 alive also creates a maintenance burden for HubSpot's engineering team. Deprecating it lets them move faster on features that actually matter to the humans running their businesses on HubSpot every day.
The underlying frustration this creates is real, though. Discovering a deprecated API often means hunting through custom integrations, legacy apps, or a developer's old code to figure out what's calling V1. That audit work takes time your team might not have budgeted.
How to Use It Step by Step
Here's the migration path. Work through these in order so nothing falls through the cracks.
- Audit every integration that touches HubSpot pipelines. Check custom-built apps, third-party connectors, Zapier or Make automations with HubSpot API steps, and any internal scripts your dev team wrote. Look for any call to the Pipelines V1 endpoint.
- Review the Pipelines API 2026-09 documentation on HubSpot's developer portal. Note what changed in the request and response shapes compared to what your current code expects.
- Update your API calls to point to the 2026-09 version. Adjust any request parameters, authentication headers, or response parsing that the new version handles differently.
- Test in a sandbox or developer account before pushing to production. Confirm that pipeline reads, writes, and stage updates all behave as expected with the new version.
- Deploy to production by November 4, 2026. That's 30 days before the hard cutoff. It gives you a window to catch anything that slipped through testing without scrambling at the deadline.
- Document what you changed. A short internal log of which integrations were updated and when will save you hours if something breaks later and you need to trace it.
What It Touches in Your HubSpot Strategy
This deprecation isn't just a developer task. It ripples into several areas of your HubSpot setup.
Deal pipelines in Sales Hub are the most common target. If you use a custom integration to create or update deal stages automatically, that's almost certainly touching the Pipelines API. A broken call there means deals stop moving, reps lose visibility, and your pipeline reporting goes stale.
Ticket pipelines in Service Hub are the second most common exposure. Support operations that auto-route tickets into stages through API calls will fail silently if V1 goes dark and nothing's been updated.
Custom object pipelines are a growing pattern in more mature HubSpot portals. If your RevOps team built pipeline structures for custom objects, those API calls need auditing too.
Key Takeaway
Any broken Pipelines API call doesn't just fail in isolation. It can stall deals, corrupt stage data, and throw off the reports your leadership team reads every week. Fix this before it becomes a data credibility problem.
This is also a good moment to review how your CRM data flows more broadly. If your integrations are calling outdated endpoints, there's a decent chance other parts of your data stack deserve a look too. Cleaner property histories and sharper CRM records become more valuable when your integrations are reliably writing the right data. The property history table updates HubSpot shipped earlier this year make it much easier to catch and fix bad data written by misbehaving integrations, which is exactly the kind of cleanup that often surfaces during a migration like this.
Key Takeaway
Schedule your migration for November 4, 2026 at the latest. That 30-day buffer before the December 4 cutoff is your safety net. Don't treat December 4 as the target date.
RevOps teams should also think about this through the lens of automation hygiene. If you've been building workflows and automations on top of unreliable integration layers, the CRM data that feeds those workflows is only as good as what the API writes into it. Workflows built on stale or broken pipeline data will misfire.
Who Should Care Most
Not every HubSpot account will feel this equally. Here's who needs to move fast.
- RevOps and marketing ops leaders who own custom integrations between HubSpot and other platforms like Salesforce, NetSuite, or proprietary internal systems.
- Developers and technical admins who built or maintain custom HubSpot apps, private apps, or API-based automations.
- HubSpot partners and agencies managing portals for multiple clients, especially if they've deployed standardized integrations across accounts. One update needs to roll out everywhere.
- Owners of growing companies who've inherited a HubSpot portal with integrations built by a previous team or contractor and may not have full visibility into what's calling what.
- Humans running Service Hub operations with automated ticket routing through API-based logic, where a silent failure would mean support requests falling into a void.
If you're using HubSpot entirely through the native UI with no custom integrations or API connections, this deprecation doesn't affect you at all. You can skip the migration entirely.
George's Take
API deprecations are the kind of update that's easy to scroll past because they feel like a developer problem, not a business problem. But I've seen what happens when these deadlines slip inside a busy portal. A deal integration stops writing stage data. Nobody notices for two weeks. Then the VP of Sales looks at the pipeline report and nothing makes sense. Suddenly it's a credibility problem, not a technical one. The humans running these businesses deserve a CRM they can trust, and that trust starts with the plumbing working correctly.
“API deprecations feel like a developer problem right up until the moment your pipeline report stops making sense. Then they're everyone's problem. Migrate early and spare your team the scramble.”
If you want to connect this update to the bigger picture of keeping your HubSpot data accurate and actionable, take a look at how we think about conditional property logic to keep your CRM data clean as pipelines evolve. Solid pipeline architecture and clean conditional logic go hand in hand.
If you're not sure whether your portal is calling the Pipelines API V1, or you want a second set of eyes on your integration stack before the deadline, that's exactly the kind of audit we do at Sidekick Strategies. Book a strategy call and we'll help you find what needs fixing before December 4 forces your hand.
Frequently Asked Questions
What is the HubSpot Pipelines API V1 deprecation?
HubSpot is permanently shutting down the Pipelines API V1 on December 4, 2026. After that date, any integration or app that calls V1 will stop working entirely. All HubSpot accounts that use the Pipelines API V1 are affected. The replacement is the 2026-09 version of the Pipelines API, which is available now.
What breaks if I don't migrate from Pipelines API V1 before December 4, 2026?
Any integration, custom app, or automated workflow that calls the Pipelines API V1 will fail completely after December 4, 2026. This could mean deals stop updating, ticket pipelines stop routing, and pipeline reports show stale or incorrect data. There's no grace period after the cutoff date.
How do I know if my HubSpot account uses the Pipelines API V1?
Check your custom integrations, third-party connectors, private apps, and any scripts or automations built by developers. Look for API calls referencing the Pipelines V1 endpoint. If you inherited a portal from a previous team or agency, audit their technical documentation or ask your developer to search the codebase.
What's different about the Pipelines API 2026-09 version?
The 2026-09 version aligns with HubSpot's current API architecture, which means more consistent response shapes, better error handling, and support for newer platform features. Review HubSpot's developer documentation for a full comparison of request and response changes before updating your code.
When should I actually complete the migration, before December 4?
HubSpot recommends completing your migration by November 4, 2026, one full month before the hard cutoff. That buffer gives your team time to catch issues in production without scrambling at the deadline. Treat November 4 as your target date, not December 4.
Does this affect HubSpot accounts that don't use any custom integrations?
No. If your team uses HubSpot entirely through the native product interface with no custom integrations, private apps, or API-based automations connecting to pipelines, this deprecation has no impact on you. Only accounts with programmatic connections to the Pipelines API need to act.
