.png){kind=logo}
getting this error while integration with phantombuster
getting this error while integration with phantombuster
If you're getting a "Body parse output" 400 error with Phantombuster integration, here are the key steps to resolve it: 1. Check your key formatting: • Ensure all keys are surrounded by double quotes • If using dynamic column values, make sure the dynamic column tags have quotes around them 2. Review syntax carefully: • Verify all keys are properly separated by commas • Check for any extra spaces, colons, or brackets • Make sure all punctuation is correct 3. Check for hidden characters: • Copy and paste your body content into a text editor • Look for any hidden or unexpected characters that might be causing the error 4. Verify API key: • Confirm you're using the correct API key • This is especially important if you're working with multiple API keysIf you need to combine plain text with a dynamic column tag, first create a Formula column to combine them, then include that column (with quotes) in your body tag. Sources: HTTP API integration overview | Documentation | Clay University HTTP API with JWT authentication | Documentation | Clay University
Did that answer your question?
Here's how to fix the "Body parse output" 400 error: 1. Check your JSON formatting: • Ensure all text values are in double quotes (e.g.,
"name": "John") • Numbers don't need quotes (e.g.,"age": 30) • Remove any trailing commas at the end of objects 2. For dynamic column values: • Add quotes around dynamic column tags for string values • If combining plain text with dynamic column tags, create a Formula column first 3. Review your syntax: • Verify all keys have proper commas between them • Check for extra spaces, colons, or brackets • Look for any hidden characters by pasting into a text editorHere's an example of correct formatting:LBKS{ "name": "John", "age": 30 }LBKSYou can validate your JSON using a tool like JSONLint to spot any formatting issues. Sources: HTTP API integration overview | Documentation | Clay University FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment?Was that helpful?