Troubleshooting HTTP API: Failed to Parse Body Input Error

Dustin S.

Hi team, I'm having issues with HTTP API - getting error message "Failed to parse body input".

27 comments

· Sorted by Oldest

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!
Dustin S.
·
·
I also set up some test columns. In this very simple test, I am getting the same error. Oddly enough, when I add quotes around the value here, I get a 200. I made another test column with quotes around every value - that also returns the same error. I also have "remove empty values" selected. TIA!
Loading attachments
Dustin S.
·
·
https://app.clay.com/workspaces/292487/workbooks/wb_dR3XZmxb4xfy/tables/t_oqWPxbWDr7i7/views/gv_f5NvqrNdeKtV
Arturo O.
·
·
Hey Dustin, thanks for the message and letting us know! Your first couple of columns are configured correctly but when some of the optional inputs are empty it could cause issues. Our team will release an update very soon to address that without requiring a more technical workaround. I'll check if it will be released today to test it out, and let you know in a few. Appreciate your patience!
Dustin S.
·
·
Hey Arturo O., Really appreciate you getting back to me. Fingers crossed it will be released soon! Thanks.
Channeled
APP
·
·
Hi Dustin S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Dustin S.
·
·
Hi Arturo O., saw this was closed - is there an update?
Channeled
APP
·
·
Hi Dustin S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Dustin S.
·
·
Hi team, I am reopening this since I had not heard back since the initial message, where I was informed I would be updated. Please let me know if I should reach out elsewhere..
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
LuisArturo
·
·
Hey there Dustin thanks for reaching out, still waiting for the update, this is the right place we will reach out inn this ticket when it goes live.
Dustin S.
·
·
Great, thanks!
Keith C.
·
·
Hi - I'm having the same problem since earlier today. Seems like by adding quotes around the variables will get away from the error. But it doesn't appear to be consistent. Sometimes removing the quotes will return 200.
Keith C.
·
·
Dustin S. looks like if the text block includes carriage return, will need to have quotes around it. If it's a single line, leave it without the quotes like before. and the best thing is that you can use the quotes the wrap around multiple variables and join them together. Maybe it's an enhancement?

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!
Dustin S.
·
·
I also set up some test columns. In this very simple test, I am getting the same error. Oddly enough, when I add quotes around the value here, I get a 200. I made another test column with quotes around every value - that also returns the same error. I also have "remove empty values" selected. TIA!
Loading attachments
Dustin S.
·
·
https://app.clay.com/workspaces/292487/workbooks/wb_dR3XZmxb4xfy/tables/t_oqWPxbWDr7i7/views/gv_f5NvqrNdeKtV
Arturo O.
·
·
Hey Dustin, thanks for the message and letting us know! Your first couple of columns are configured correctly but when some of the optional inputs are empty it could cause issues. Our team will release an update very soon to address that without requiring a more technical workaround. I'll check if it will be released today to test it out, and let you know in a few. Appreciate your patience!
Dustin S.
·
·
Hey Arturo O., Really appreciate you getting back to me. Fingers crossed it will be released soon! Thanks.
Channeled
APP
·
·
Hi Dustin S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
Dustin S.
·
·
Hi Arturo O., saw this was closed - is there an update?
Channeled
APP
·
·
Hi Dustin S.! This thread was recently closed by our Support team. If you have a moment, please share your feedback:
Dustin S.
·
·
Hi team, I am reopening this since I had not heard back since the initial message, where I was informed I would be updated. Please let me know if I should reach out elsewhere..
Channeled
APP
·
·
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
LuisArturo
·
·
Hey there Dustin thanks for reaching out, still waiting for the update, this is the right place we will reach out inn this ticket when it goes live.
Dustin S.
·
·
Great, thanks!
Keith C.
·
·
Hi - I'm having the same problem since earlier today. Seems like by adding quotes around the variables will get away from the error. But it doesn't appear to be consistent. Sometimes removing the quotes will return 200.
Keith C.
·
·
Dustin S. looks like if the text block includes carriage return, will need to have quotes around it. If it's a single line, leave it without the quotes like before. and the best thing is that you can use the quotes the wrap around multiple variables and join them together. Maybe it's an enhancement?