Okapi Okapi
Add to GitHub

HubSpot API · api.hubapi.com

HubSpot API v1 deprecations

The breaking changes HubSpot API announced for its v1 endpoints: 8 of the 16 Okapi tracks.

Coming up 2

  1. /v1/*Version retirement Stops workingin 36 days
  2. /crm-pipelines/v1/*Version retirement Stops workingin 36 days

Deprecated, no date yet 4

  1. No date /contacts/v1/*Version retirement Deprecated, no date
  2. No date /deals/v1/*Version retirement Deprecated, no date
  3. No date /engagements/v1/*Version retirement Deprecated, no date
  4. No date /broadcast/v1/*Endpoint removal Deprecated, no date

Already in effect 2

  1. /contacts/v1/lists*Version retirement Stopped working
  2. /calendar/v1/*Endpoint removal Stopped working

Questions

Is the HubSpot API v1 deprecated?

HubSpot API has announced 8 breaking changes to its v1 endpoints: 4 with a shutdown date, 4 deprecated without one. Each one's page says what to use instead.

When do HubSpot API v1 endpoints stop working?

The next is /v1/* version retirement, on December 4, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls these changes hit and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.

Know before your API calls break.

Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.

Add to GitHub