We currently use the previous v3 version in our codebase and are just looking to confirm whether moving over to the date-versioned SDK will help future proof us against potential future deprecations coming in to v3 or v4 endpoints, as well as the OAuth1 changes I think I’ve saw if someone could help?
Based on the official documentation, it’s not particularly clear whether or when to make this transition from the semantically versioned SDK to the date-based versioned one. However, given they’ve created a new GitHub repo for access to the date-based API versions, I’d guess making the transition is a good move (and likely will be required as they sunset the semantic API versions).
I hope this helps. Please let me know if you have any follow-up questions.
Yes @TomC86, I can confirm that moving to the date-versioned PHP SDK is definitely a great choice for staying future-ready.
This migration not only aligns you with the new versioning model, but also, together with the OAuth migration, ensures you’re set up well ahead of the upcoming changes.
I hope this helps!
Have a lovely day!
Bérangère
This post was created with the assistance of AI tools
Thank you both! Beginning discovery work now on the upgrade!
Can I just confirm whether there are any immediate plans for sunsetting of the v3 endpoints e.g. anything on ‘api.hubapi.com/crm/v3/’? I can see HubSpot Projects v2025.1 being deprecated next month and was worried I might not have as much time as I thought.
