Troubleshooting JSON Errors with HTTP API Enrichment Column

miguel · 2025-02-24 14:34:35.072657+00

Hello! I'm trying to pass data using a http api enrichment column but I'm having a problem with the Body using this JSON forrmat: ```{ "linkedin_profile": Profile Url }``` And Im getting this error message: ```Failed to parse body input```

Troubleshooting JSON Errors with HTTP API Enrichment Column | Clay

9 comments

· Sorted by Oldest

Channeled
APP
·
·
The error occurs because of incorrect JSON formatting in your Body section. Here's how to fix it: 1. Make sure to enclose both the key and value in double quotes: LBKS{ "linkedin_profile": "Profile Url" }LBKS2. If you're using a dynamic column as the value, you must include quotes around the dynamic column tag. Some additional tips to avoid this error: ** Check for any extra commas at the end of lines ** Be mindful of spaces, colons, and brackets * Consider pasting your JSON into a validator like JSONLint to check the formatting Note: As of October 2024, you must enclose dynamic string variables in quotation marks when using the HTTP API enrichment column.
Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
miguel
·
·
Muhammad
·
·
Try
{ "linkedin_profile": "Profile Url" }
Channeled
APP
·
·
Based on your JSON format, here's how to fix the "Failed to parse body" error: 1. Make sure both the key and value are enclosed in double quotes: LBKS{ "linkedin_profile": "Profile Url" }LBKSKey points to check: • No extra commas at the end • Proper spacing around colons • Correct placement of brackets • No hidden characters If you're using a dynamic column value (like /column), remember that as of October 2024, you must still enclose it in quotation marks. For additional validation, you can paste your JSON into a validator like JSONLint to check the formatting.
Sources: HTTP API with JWT authentication | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Channeled
APP
·
·
Is that what you were looking for?
miguel
·
·
yes thank you so much
Channeled
APP
·
·
I'm delighted to hear that! I'm here if you need any further assistance.
Channeled
APP
·
·
Hi miguel! This thread was recently closed by our Support team. If you have a moment, please share your feedback:

Channeled
APP
·
·
The error occurs because of incorrect JSON formatting in your Body section. Here's how to fix it: 1. Make sure to enclose both the key and value in double quotes: LBKS{ "linkedin_profile": "Profile Url" }LBKS2. If you're using a dynamic column as the value, you must include quotes around the dynamic column tag. Some additional tips to avoid this error: ** Check for any extra commas at the end of lines ** Be mindful of spaces, colons, and brackets * Consider pasting your JSON into a validator like JSONLint to check the formatting Note: As of October 2024, you must enclose dynamic string variables in quotation marks when using the HTTP API enrichment column.
Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? HTTP API with JWT authentication | Documentation | Clay University HTTP API integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
miguel
·
·
Muhammad
·
·
Try
{ "linkedin_profile": "Profile Url" }
Channeled
APP
·
·
Based on your JSON format, here's how to fix the "Failed to parse body" error: 1. Make sure both the key and value are enclosed in double quotes: LBKS{ "linkedin_profile": "Profile Url" }LBKSKey points to check: • No extra commas at the end • Proper spacing around colons • Correct placement of brackets • No hidden characters If you're using a dynamic column value (like /column), remember that as of October 2024, you must still enclose it in quotation marks. For additional validation, you can paste your JSON into a validator like JSONLint to check the formatting.
Sources: HTTP API with JWT authentication | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?
Channeled
APP
·
·
Is that what you were looking for?
miguel
·
·
yes thank you so much
Channeled
APP
·
·
I'm delighted to hear that! I'm here if you need any further assistance.
Channeled
APP
·
·
Hi miguel! This thread was recently closed by our Support team. If you have a moment, please share your feedback: