v4
Breaking Changes2
Public Legacy APIs
Several public legacy APIs were removed. This impacts integrations still relying on older endpoints that have been superseded by newer, more robust versions. Developers must migrate to the current API versions to maintain functionality.
Calls to legacy endpoints like /forms/v2/forms and /files/v3/files.
Calls to updated endpoints like /forms/v2/definitions and POST /crm/v3/objects/files.
Update all calls to legacy endpoints to their current, documented replacements.
OAuth Scopes in Token Response
The `scopes` property was removed from the OAuth token response. This change was made to reduce the size of the token response and align with best practices. Applications should no longer rely on parsing scopes from the token response.
OAuth token response includes a `scopes` array.
OAuth token response no longer includes the `scopes` array.
Fetch scopes separately using the `GET /oauth/v1/access-token/{token}` endpoint if needed.
Migration Checklist
Full interactive checklist →- 1Identify and document all legacy HubSpot API endpoints currently used in your integration.
- 2Review the HubSpot API v4 documentation for replacements to identified legacy endpoints.
- 3Update integration code to call the new, non-deprecated endpoints for all legacy API interactions.
- 4If your integration relies on OAuth scopes from the token response, update it to fetch scopes separately.
- 5Test all updated API interactions thoroughly in a staging environment.
- 6Deploy the updated integration to production.
- 7Monitor integration performance and error logs post-deployment to confirm successful migration.
Never get blindsided by an API change again
Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.
Join the Waitlist