Date-based versioning changes the API resource path, but does it change authentication or OAuth

Smart CRM & Sales Hub CRM
1

ShubhangiPawar

4d

OP

we also looking more confirmation on below points @chighsmith

The key section says: date-based versioning changes the API resource path, but it does not change authentication or OAuth scopes.
Old CRM call: /crm/v3/objects/contacts
Date-based CRM call: /crm/objects/2026-03/contacts
OAuth stays the same:authorize user: https://app.hubspot.com/oauth/authorize
get/refresh tokens: https://api.hubapi.com/oauth/v3/token

Use the returned access token in both cases:
Authorization: Bearer <access_token>
Managing OAuth remains the same:
Send the user to the authorize URL.
HubSpot redirects back with an authorization code.
Exchange the code at /oauth/v3/token.
Store the access and refresh tokens securely.
Refresh the access token with the same /oauth/v3/token endpoint when it expires.
Use the access token to call either v3 or date-based CRM APIs.
The only related change is scopes: the date-based endpoint still needs the appropriate existing CRM scope, such as crm.objects.contacts.read or crm.objects.contacts.write.
HubSpot’s OAuth reference is here: Manage OAuth access tokens using the v3 APIs.

please confirm does above information is latest and correct. there is no change in oauth related api for date based versioning.

3

My read from the current docs: the CRM call path changes for date-based endpoints, but the OAuth install flow and bearer-token pattern are not replaced by CRM path versioning itself.

One correction: I would not keep /oauth/v3/token in new migration notes. HubSpot’s current OAuth token reference shows the date-based token endpoint as POST https://api.hubapi.com/oauth/2026-03/token, while the authorize URL is still the app.hubspot.com/oauth/authorize flow. So the token still carries the granted scopes and you still use Authorization: Bearer … on the CRM call, but token management should be updated if you are also moving to the latest OAuth docs.

I’d check each date-based endpoint’s required scopes separately rather than assuming every old call maps 1:1.

Docs I checked: 2026-03 API reference - HubSpot docs and Refresh an access token - HubSpot docs

Disclosure: drafted with AI assistance.