Confusing Behavior When Inserting Columns in JSON via HTTP Tool

Not sure if you guys would consider this to be a bug, but I definitely found this behavior to be confusing and unintuitive… When inserting a column in a JSON body using the HTTP tool, it appears that strings automatically get inserted with quotes around them. However, the same does not appear to be true for formula columns that output a string. Took me awhile to figure out what the heck was wrong since the error message was a bit vague (“Failed to parse body input”), there’s no ability to trace the full HTTP lifecycle, and the docs are a little lacking when it comes to the formula DSL.

5 comments

Channeled
APP
·
·
As of October 2024, you must enclose dynamic string variables in quotation marks when using the HTTP API enrichment column, including formula columns.When referencing dynamic variables using /column, you need to follow JSON formatting rules:** String values must have quotation marks ** Numbers don't need quotes (except for numbers with trailing zeros like "0004") * If you need to combine plain text with a dynamic column tag, create a Formula column first, then include that column with quotes in your body tag Sources: HTTP API - Clay University HTTP API with JWT Authentication - Clay University
John M.
·
·
Whoa. This bot is scary good. Okay, so perhaps I’m wrong and regular text columns no longer get inserted with quotes included. (This is a smart change IMO) I can’t remember where I saw this mentioned in the docs, but it was definitely mentioned somewhere. One of the blog posts I think. I’ll post it here if I can find it so maybe someone can update it.
Channeled
APP
·
·
I appreciate your feedback, and I'd be interested to see that documentation if you find it, as we always aim to keep our information up-to-date and accurate.
Channeled
APP
·
·
Hi John M.! 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 John M.!