LinkedIn Profile Scraping Issues with RapidAPI Explained
not sure what this means... I'm doing some LinkedIn profile scraping using a rapidapi API. It's been working up until now on my other tables
not sure what this means... I'm doing some LinkedIn profile scraping using a rapidapi API. It's been working up until now on my other tables
The "failed to parse body" error typically indicates there's an issue with the JSON formatting in your API request body. Here's how to resolve it: 1. Check your JSON formatting: • Ensure all strings are enclosed in quotes • Remove any trailing commas • Verify proper syntax for numbers and booleans (no quotes needed)Quick troubleshooting steps: ** Look for hidden characters or extra spaces ** Verify all keys are properly separated by commas * Double-check your brackets and colonsFor a quick fix, try pasting your JSON data into a validator like JSONLint to spot formatting issues.Note: Keep in mind that LinkedIn data might be limited or inaccurate since data providers don't use active sessions or cookies to scrape LinkedIn data live - some fields are only visible when logged in. 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
To resolve the "failed to parse body" error, check these key areas in your API request body: 1. Text Formatting:
• Ensure all text values are enclosed in double quotes
• Example: "name": "John" instead of name: John
2. Syntax Elements:
• Remove any trailing commas at the end of objects
• Verify proper comma separation between keys
• Check for correct placement of colons and brackets
3. Data Cleanup:
• Copy your body content into a text editor to spot any hidden characters
• If using dynamic column values, make sure they're properly quoted
• For combined values, create a Formula column firstFor quick validation, paste your JSON data into a tool like JSONLint to identify 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?
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!
Hi Benyamin, thanks for reaching out! Clay has a hard cell size limit of 8KB (or 8,000 characters) for all cells. This is a core system constraint we can't modify
To workaround this error, we recommend that you parse the data before pulling it into your clay table
https://rapidapi.com/rockapis-rockapis-default/api/linkedin-api8 this is the API if it matters and this is a successful pull from another table doing the same thing - when cells are formatted like this does it not change the way that limit is calculated?
Benyamin, could you send this table url?
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 Clay Support.