Replies: 2 comments 1 reply
-
I've found this to often work for me, but sometimes not - depending on the API that I'm using. Usually, the solution is to add the headers:
I actually think we should set these headers by default. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi @mjashanks I have those in my headers, as stated in the original question. However, that also doesn't do the trick, unfortunately. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For some reason my endpoint return data isn't parsed as json by default. I have tried it in other apps like n8n where the return data is parsed properly. I have also tried explicitly setting both the Accept:application/json and Content-Type:application/json headers. Currently I have to run
return JSON.parse(data)
in the transformer function to have the data parsed as JSON. I'm wondering why that happens though and why I need to take that extra step? Any thoughts?Beta Was this translation helpful? Give feedback.
All reactions