HTTP API Calls Returning Failed to Parse Body Error - Clay Issue | Clay

HTTP API Calls Returning Failed to Parse Body Error - Clay Issue

Getting "Failed to parse body" on HTTP API calls that are in there correctly - seems to be a clay issue and not the provider

17 comments

Channeled
APP
·
·
👋 Hey there! Our support team has got your message - we'll be back in touch within 24 hours (often sooner!). If you haven't already, please include the URL of your table in this thread so that we can help you as quickly as possible!
Muhammad S.
·
·
If you could share screenshot of your input body I can help you fix it real quick
Bruno R.
·
·
Hi Jeff, thanks for reaching out. Taking a look at this now.
Bruno R.
·
·
Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1729092600&signature=f81a2dcbca61601e4f97c5f6e2eebe5837ede937665c6491229c416926fc9a6d&req=dSEgF85%2FmohWX%2FMW1HO4zYTywCL8D5UQ2BKsam%2FhVPvm%2Bg%3D%3D%0A
Jeff T.
·
·
https://app.clay.com/workspaces/24851/tables/t_PwMnvMXiEsMJ/views/gv_o6G5x4ZUJpCB
Bruno R.
·
·
It looks like we've got a bug on our hands - I've escalated this over to our engineering team and we'll let you know as soon as we know more!
Jeff T.
·
·
Thanks, i'll keep an eye out for an update
Tanvi R.
·
·
Hi Jeff! Happy to report that we heard back from the team and this issue should be fixed. Thank you for your patience, feel free to try again and let us know if the problem has been resolved on your end.
1
Channeled
APP
·
·
Hi Jeff T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thank you so much for sharing your feedback Jeff T.!
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Jeff T.
·
·
I just tried again and it's not working
LuisArturo
·
·
Hey there Jeff thanks for reaching out, addressed the issue for you in your table, what happened there was a recent update to the integration and now any columns that contain strings require quotations around them as shown in the screenshot below. Moving forwards all inputs that are used that are strings will need quotations however numbers and true/false response do not require them. https://downloads.intercomcdn.com/i/o/w28k1kwz/1218683929/245b1110758d3dd06674c5d8f58b/image.png?expires=1729118700&signature=fa94f2577e9b88e0a093ba646ce4852e40fd907addeb7f4d9f0d95b52e447c90&req=dSImHs92nohdUPMW1HO4zShZqnMFtbFlGlrsEtFFGeMV2NaGBOwj%2FVnxbThF%0ATV7v%0A
Jeff T.
·
·
Ah thanks. Is that going to change again? Out of curiosity, why'd that change? The docs all say "DONT" use quotes around the blocks.
LuisArturo
·
·
Hey there Jeff, thanks for pointing this out about the docs, will make sure this gets updated. There was a recent update to our HTTP API integration that changed how the integration works, with one of the side affects being that quotes are now required in the body.
Channeled
APP
·
·
Hi Jeff T.! This thread was recently closed by our Support team. If you have a moment, please share your feedback: