HubSpot API
Marketing Calendar API removal
Stopped workingSubscribe to HubSpot APIShare
On August 31, 2023, endpoints matching /calendar/v1/* were removed. Calls made to these endpoints after that day fail. You can continue to use the marketing calendar in HubSpot itself, but programmatic access is no longer supported.
Calls it hits
/calendar/v1/*
What to use instead of these calls
No API replaces it, as HubSpot offers no API in its place. Use the marketing calendar in HubSpot's app instead.
HubSpot offers no API in its place.
In HubSpot API's words
Marketing calendar | August 31, 2023 | You can continue to use the marketing calendar in HubSpot.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Removal
- Takes effect
- August 31, 2023
- 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 /calendar/v1/* on HubSpot API stopped working on August 31, 2023.
What happens to calls after August 31, 2023?
They have failed since August 31, 2023.
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 -
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 -
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.