Troubleshooting JSON Stringification for HTTP API Action in Enrichment

Brandon G. · 2025-01-03 21:17:00.207643+00

Hi - I'm trying to pass a JSON response I get from an enrichment into the HTTP API action. The api expects the JSON to be stringified and I can't seem to pass it as a string. When I try to use a Formula to convert it via JSON.stringify(/reference-to-field), it shows it in the text field but the values aren't stringified. I can't use JSON.stringify in the actual body of the request.

Troubleshooting JSON Stringification for HTTP API Action in Enrichment | Clay

6 comments

· Sorted by Oldest

Channeled
APP
·
·
When using dynamic variables in the HTTP API body, you need to follow specific JSON formatting rules: 1. For string values, enclose both the key and the dynamic column reference in quotes: "key": "/column" 2. If you need to combine text with a dynamic column value or modify the format, create a separate Formula column first to handle the combination/formatting, then reference that Formula column in your HTTP API body (with quotes).If you're still getting parsing errors, try these troubleshooting steps: 1. Check for any extra spaces, commas, or hidden characters 2. Verify your JSON syntax is correct using a tool like JSONLint 3. Make sure all keys are properly quoted and separated by commas Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Anaum K.
·
·
Hello Brandon! Thank you for reaching out! 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=1735946100&signature=19d04ca5b931d961add835a796985cd0d1190e1a4ef4ba138a0fc097ab218c44&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS71ApEX2BKsam%2FhVPvxlg%3D%3D%0A
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

shivam

hey Anaum K. what is the solve here ? I am facing the same problem : I have a json object and I want to pass it to HTTP api which needs a string, so in js we do something like : JSON.stringify example this json [data] :

{"White": 37, "Black or African American": 27, "Hispanic or Latino": 31, "Asian": 1, "American Indian/ Alaska Native": 0, "Native Hawaiian and Other Pacific Islander": 1, "Some other race alone": 0, "Two or more races": 3}

would become this with JSON.stringify(data) :

"{\"White\": 37, \"Black or African American\": 27, \"Hispanic or Latino\": 31, \"Asian\": 1, \"American Indian/ Alaska Native\": 0, \"Native Hawaiian and Other Pacific Islander\": 1, \"Some other race alone\": 0, \"Two or more races\": 3} "

any way to achieve this ?

shivam
·
·
Clay S. do you know how to solve this ?

Loading comments

Channeled
APP
·
·
When using dynamic variables in the HTTP API body, you need to follow specific JSON formatting rules: 1. For string values, enclose both the key and the dynamic column reference in quotes: "key": "/column" 2. If you need to combine text with a dynamic column value or modify the format, create a separate Formula column first to handle the combination/formatting, then reference that Formula column in your HTTP API body (with quotes).If you're still getting parsing errors, try these troubleshooting steps: 1. Check for any extra spaces, commas, or hidden characters 2. Verify your JSON syntax is correct using a tool like JSONLint 3. Make sure all keys are properly quoted and separated by commas Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Channeled
APP
·
·
Looks like you're still looking for help. We're escalating this over to our support team and someone should be in touch soon. In the meantime, feel free to include any other information that may be helpful in solving your issue!
Anaum K.
·
·
Hello Brandon! Thank you for reaching out! 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=1735946100&signature=19d04ca5b931d961add835a796985cd0d1190e1a4ef4ba138a0fc097ab218c44&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS71ApEX2BKsam%2FhVPvxlg%3D%3D%0A
Channeled
APP
·
·
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.

shivam

{"White": 37, "Black or African American": 27, "Hispanic or Latino": 31, "Asian": 1, "American Indian/ Alaska Native": 0, "Native Hawaiian and Other Pacific Islander": 1, "Some other race alone": 0, "Two or more races": 3}

would become this with JSON.stringify(data) :

"{\"White\": 37, \"Black or African American\": 27, \"Hispanic or Latino\": 31, \"Asian\": 1, \"American Indian/ Alaska Native\": 0, \"Native Hawaiian and Other Pacific Islander\": 1, \"Some other race alone\": 0, \"Two or more races\": 3} "

any way to achieve this ?

shivam
·
·
Clay S. do you know how to solve this ?