I can't seem to replicate what you are seeing. For instance with the below code in a custom coded workflow action where 2-106192594 is the custom object schema ID for "Orders" in my test portal:
Did you try running this code in an isolated workflow action without other code or logic, or is your provided example part of a larger code block? On the surface there really isn't any reason your result should be coming back that way as far as I can tell.
What's odd to me is "response.data" should contain a large JSON object that isn't unique to HubSpot. It should be Axios' standard response object. So your code resulting in what you posted tells me either there is some other logic outside of what you shared acting on the Axios object, or HubSpot was/is having some underlying issue when you were working on this. I don't see how it would have anything to do with the API itself.
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 !