topic Re: Parsing Axios response from an API call in APIs & Integrations

Parsing Axios response from an API call

PAtlan — Thu, 01 Dec 2022 13:02:41 GMT

I'm trying to get some information from a contact in custom code for a workflow.

I've set up a local environment to test my code.

If I use fetch, I can access my HubSpot portal and get the information I need.

If I use the same route with Axios, the data I get is gibberish.

Here's a code sample:

This returns :

!� �RY�0~�f��/7��@V�9��zBq1{�,��ή/�Pn� application/json;charset=utf-8

The same route, with the same Authorization, using fetch, returns:

{ results: [ { id: '491582160', type: 'site_to_contact' } ] }

I'm really not sure what I'm doing wrong. And because I can't seem to use fetch in a Hubspot Workflow code block, I really need to figure it out.

Thanks !

Re: Parsing Axios response from an API call

Jaycee_Lewis — Thu, 01 Dec 2022 20:33:26 GMT

Hi, @PAtlan 👋 Thanks for the question. Hey, @LMartinez7 @LeeBartelme, do you have any suggestions for @PAtlan?

Best,

Jaycee

Re: Parsing Axios response from an API call

LeeBartelme — Thu, 01 Dec 2022 20:48:50 GMT

Try setting the "Accept" headers to "application/json".

Re: Parsing Axios response from an API call

PAtlan — Thu, 01 Dec 2022 21:13:05 GMT

Thanks for your reply, but no joy.

Re: Parsing Axios response from an API call

coldrickjack — Fri, 02 Dec 2022 12:53:40 GMT

Hey @PAtlan,

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:

I get the following response:

results: [ { id: '267226578', type: 'order_to_contact' }, { id: '267234515', type: 'order_to_contact' } ]

Also can you link to the documentation for the endpoint you have included within your example? I'm not able to find it on the developer docs.

Re: Parsing Axios response from an API call

LeeBartelme — Fri, 02 Dec 2022 14:02:44 GMT

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.