HubSpot API
Social Media API removal
Deprecated, no dateSubscribe to HubSpot APIShare
HubSpot has deprecated the legacy /broadcast/v1/* endpoints without a shutdown date. HubSpot API notes that these endpoints are functional and stable, but will not be updated beyond their current version. Any eventual removal will cause requests to these endpoints to fail.
Calls it hits
/broadcast/v1/*
What to use instead of these calls
No replacement is announced, and the endpoints keep working. Because HubSpot names no replacement for its social publishing endpoints, a decision on alternative approaches is needed.
HubSpot names no replacement for its social publishing endpoints.
In HubSpot API's words
The legacy endpoints listed below will not be getting a version update. These endpoints are functional and stable, but won’t be updated beyond their current version.
Facts
- API
- HubSpot API
api.hubapi.com - Kind
- Removal
- 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 /broadcast/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.