.png){kind=logo}
Troubleshooting HTTP API: Failed to Parse Body Input Error
Hi team, I'm having issues with HTTP API - getting error message "Failed to parse body input".
Hi team, I'm having issues with HTTP API - getting error message "Failed to parse body input".
👋 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!
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!
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!
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
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..
Thanks! We've reopened this thread. You can continue to add more detail directly in this thread.
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.
Great, thanks!
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.
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?
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?
Hey, thanks for reaching out - Can you send us the table url so we can check?
Yes, this is an enhancement our team has been testing, and we’ll be announcing it soon. It looks like everything is working as expected now, right? 😊
Bo (. great to know it there'll be an update. The text limit per variable can finally be handled from within. But I'm still not too sure when do we need to put the quotes. In this example, if I put the quotes to wrap the email value, it will return parsing error. And also if i remove the quotes from the other values like firstName, lastName etc (they are all single line short text), it will also return error. Yet I have another HTTP module in another table, it's completely fine using the old syntax. Did you guys rolling this feature out by table creation date or something? It's quite difficult for me to determine what works and what doesn't...
Hey Dustin can you send us the table url? Great question btw! The update introduced a requirement where strings need to be wrapped in quotes, but numbers, booleans, and objects don’t. This is part of the new JSON handling feature, which makes it easier to parse inputs correctly. If you’re getting a parsing error with the email value wrapped in quotes, it could be due to how the data type is recognized so would like to take a look. Let me know
Here you go! Bo (. https://app.clay.com/workspaces/292487/workbooks/wb_dR3XZmxb4xfy/tables/t_oqWPxbWDr7i7/views/gv_f5NvqrNdeKtV Thanks. Do strings need to be wrapped in quotes even when using dynamic variables?
Got it to work now! Thanks for your help. This can be closed
awesome! thanks for the great update!