We have been successfully using the v1 apis to create emails and perform related tasks such as lookup lists and subscriptions. In the past week we have started to see features break or begin to exhibit new unexpected error messages.
I have read as many changelogs as I can find and familiarized myself with the v3 endpoints. We will try to go that way asap but I was not expecting things to be break/fail as they have.
Two examples of the issues we see are:
/marketing-emails/v1/emails/
We create a new email using the endpoint. We populate the lists, using the old list ids here and I can see 2 of the “newer” style fields have appeared in the reponse but this call no longer updates the lists in the hubspot ui like is used to.
/email/public/v1/subscriptions
This endpoint is now very picky about “business unit ids” and throws new errors asking for a matching business unit. I’m up to date with the v3 direction but it was my impression the v1s would still be working for a bit longer.
We’re working on a migration path to v3 right now but it would be really helpful to have access to the business ids feature in our dev sandbox #7254124 so we can fully test this new functionality.
Thanks for your post. That sounds unexpected, for sure. Can you share an example of each, please? The request, request body (if applicable), the response, and any errors you get back are all things my internal resources like to have when reporting product issues. Doing it in Postman might be a simple way to do that. But whatever is best for you is fine.