Pipelines API: Validate Pipeline & Pipeline Stage Usages
Monday, September 14, 2026
What it is
Deleting a pipeline or a pipeline stage through the public Pipelines API now checks whether it is in use first, the same check HubSpot Settings already runs. If the pipeline or stage still has records on it, the delete request gets blocked instead of going through.
Why it matters
A handful of recent API betas have gone the other direction, tightening a constraint on the API that the UI already enforced without warning anyone building against it. This one closes a real gap: an API delete call used to have less protection than the same action taken by hand in Settings, which means a script could have removed a stage with live records on it. Neither host had actually hit that failure mode, which is the point. Now they cannot.
The Take
The title reads like plumbing, and it is, but the plumbing matters here. An API delete call used to be able to do something the UI would stop you from doing by hand, remove a pipeline or a stage that still had records sitting on it. That gap is closed now. If you have ever built a deployment script that touches pipelines, this is the kind of update you do not notice until the day it saves you, so add it to the list of things you no longer need a manual safety check for.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
What changed?
A delete request against a pipeline or a pipeline stage through the public Pipelines API now checks whether it is in use first, and gets blocked if it is, matching the check HubSpot Settings already runs.
Does this affect existing scripts?
Only if a script tries to delete a pipeline or stage that still has records on it. That request will now fail where it might have succeeded before.
Do I need to change anything to get this?
No. This is a validation change on HubSpot's side of the API, not something you configure.
Produced by Value-First Media