HubSpot API
/automation/v4/* version retirement
Deprecated, no dateSubscribe to HubSpot APIShare
HubSpot deprecated the /automation/v4/* endpoints without announcing a specific shutdown date. HubSpot API announced that in March 2027, v4 APIs will move to an unsupported state and will no longer receive updates, bug fixes, or stability guarantees. Calls to these endpoints will eventually fail.
Calls it hits
/automation/v4/*
What to use instead of these calls
Move to the latest date-based API version, 2026-09.
In HubSpot API's words
In March 2027, HubSpot v4 APIs will move to an unsupported state. After that date, v4 APIs will no longer receive updates, bug fixes, or stability guarantees from HubSpot.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Announced
- May 21, 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 /automation/v4/* 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
/companies/v2/*Version retirement Deprecated, no date -
No date
/contacts/v1/*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.