Skip to content
Shows/Engineering the Business
Engineering the Business·Episode 1·Series

What's New in the HubSpot API

Recent changes every integrator should know

Jan 20, 2026·38:00·Buzco Stanislav, Paul Maxwell

Video coming soon

No YouTube video has been added yet.

Your browser does not support the audio element.

About this episode

Paul and Buzco go hands-on with the latest HubSpot API changes: new endpoints, deprecations, and the patterns that make integrations more resilient. Includes a starter repo to follow along.

Key ideas

  • 01The API is a contract that changes; track the changelog
  • 02Build retries, backoff, and error handling from the first commit
  • 03Real traffic means rate limits, retries, and partial failures
  • 04Production readiness is mostly about behavior when things go wrong

Show notes

What we covered

The HubSpot API keeps evolving, and integrators who don't keep up ship brittle code. Paul and Buzco walk through the recent changes that matter, with real examples and a starter repo you can clone to try them yourself.

In this episode

  • The new and updated endpoints worth adopting
  • Deprecations you need to migrate off
  • Auth and rate-limit patterns that hold up in production
  • Error handling that survives real-world traffic
  • Cloning and running the starter repo

Links & resources

  • HubSpot API Starter Repo (downloadable)
  • HubSpot developer changelog
  • Buzco's notes on resilient API clients

Timestamps

Chapters

  1. —The API as a contract
  2. 6:00New endpoints
  3. 15:00Deprecations to migrate
  4. 24:00Auth and rate limits
  5. 32:00Running the starter repo

Quotable

“The difference between a demo integration and a production one is how it behaves when things go wrong.”

— Buzco Stanislav

Full transcript

Transcript~1 min read

Show transcriptHide transcript

Paul: APIs are a contract, and HubSpot updates that contract regularly. If you're not tracking the changelog, you're one deprecation away from a broken integration and a bad Monday.

Buzco: The thing people get wrong is treating the happy path as the whole path. Real traffic means rate limits, retries, and partial failures. Your client has to expect all of it.

Paul: So in the starter repo we build in retries with backoff and proper error handling from the first commit. Not as a cleanup step later, as the foundation.

Buzco: Because the difference between a demo integration and a production one is almost entirely how it behaves when things go wrong.

Mentioned

  • HubSpot
  • Postman

Related links

  • HubSpot developer changelog

Hosts

  • BS
    Buzco Stanislav

    Host

    CTO, RevOps HQ

  • PM
    Paul Maxwell

    Host

    CEO, RevOps HQ

Topics

  • APIs
  • HubSpot
  • Software Engineering

Downloads & resources

  • HubSpot API Starter RepoRepository

Subscribe to Engineering the Business

  • YouTube
  • GitHub
  • Spotify

Related episodes

Engineering the BusinessHubSpot UI ExtensionsPaul and Buzco build a custom HubSpot UI extension live: rendering data, wiring actions, and shipping a card that lives right inside the record. Includes a working code sample.
Engineering the BusinessIntegration ArchitecturePaul and Buzco get into the architecture of integrations: sync patterns, idempotency, error recovery, and the diagrams that keep a multi-system design comprehensible. Includes a reference diagram.
Engineering the BusinessBuilding RevPlatformPaul and Buzco open the hood on RevPlatform: the architectural decisions, tradeoffs, and lessons from building a real GTM product. A candid look at what they'd do again and what they wouldn't.
Engineering the BusinessBuilding Enterprise IntegrationsPaul and Buzco tackle what changes when integrations go enterprise: volume, security reviews, governance, and the reliability bar that doesn't forgive shortcuts. Builds on the starter repo.