HubSpot API
/engagements/v1/* version retirement
Deprecated, no dateSubscribe to HubSpot APIShare
On September 15, 2026, HubSpot deprecated the /engagements/v1/* endpoints without announcing a shutdown date. Calls to these routes will eventually fail, as numbered version paths will move to unsupported status without future bug fixes, reliability improvements, or security updates.
Calls it hits
/engagements/v1/*
What to use instead of these calls
Move to the activity object APIs on date-based versioning at /crm/objects/2026-09/{notes|calls|emails|meetings|tasks}. Because HubSpot has not finalized every legacy endpoint's date-based replacement yet, some alternatives will be documented in its March 2027 release.
HubSpot has not finalized every legacy endpoint's date-based replacement yet; it documents them in its March 2027 release.
In HubSpot API's words
Endpoints using numbered version paths, /v1/ , /v2/ , and /v3/ , will move to unsupported status. HubSpot will no longer release bug fixes, reliability improvements, or security updates for these versions.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Announced
- September 15, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against HubSpot API's own pages
Questions
When does this change take effect?
HubSpot API deprecated /engagements/v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: HubSpot API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from HubSpot API 10
-
/crm/v3/extensions/accounting/*Removal Stopped working -
/extensions/ecomm/v2/*Removal Stopped working -
/calendar/v1/*Removal Stopped working -
GET /cms/v3/performance*Removal Stopped working -
/hubdb/api/v2/*Version retirement Stopped working -
/contacts/v1/lists*Version retirement Stopped working -
/v1/*Version retirement Stops workingin 28 days -
/crm-pipelines/v1/*Version retirement Stops workingin 28 days -
No date
/automation/v4/*Version retirement Deprecated, no date -
No date
/companies/v2/*Version retirement Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.