This is breaking the code that parses into a model, as it's a string rather than an object.
I can't find any documented changes in the developer changelog so this feels more like a bug to me.
I can change the response model to work with the string that is coming back, but I don't want to do that in case it is a bug and it changes back to returning an object.
Sorry for just seeing this post now. This was a bug that we actually fixed back on July 10th. Is anyone still having issues? For posterity, HubSpot Support is the best place to report bugs of this nature (it sounds like you actually did create a Support issue and they referred you here, but I just wanted to note that Support was the best route to get a bug addressed).
Hi @Jaycee_Lewis I spoke to someone on support and they recommended I post here.
It would be useful to get a response from a Hubspot developer who can shed some light on this as it's impacting a project for a client and we're unsure of how to proceed. Thanks
Hi, @AJohnson94👋 This does sound unexpected. One question — have you already filed a support ticket for this issue?
Thanks for the additional info. — Jaycee
HubSpot’s AI-powered customer agent resolves up to 50% of customer queries instantly, with some customers reaching up to 90% resolution rates. Learn More.
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !