HubSpot API
/contacts/v1/lists* version retirement
Stopped workingSubscribe to HubSpot APIShare
On April 30, 2026, the Contact Lists API v1 was retired. Calls to endpoints matching /contacts/v1/lists* fail since that date.
Calls it hits
/contacts/v1/lists*
What to use instead of these calls
Manage lists using the Lists API at /crm/v3/lists or /crm/lists/2026-09.
In HubSpot API's words
Contact lists v1 | April 30, 2026 | Create and manage contact lists with the latest lists API.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Version retirement
- Takes effect
- April 30, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against HubSpot API's own pages
Questions
When does this change take effect?
Calls to /contacts/v1/lists* on HubSpot API stopped working on April 30, 2026.
What happens to calls after April 30, 2026?
They have failed since April 30, 2026.
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 -
/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 -
No date
/contacts/v1/*Version retirement Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.