.png){kind=logo}
How to Send LinkedIn Data in HTTP API Body Correctly
What is teh right way to send the entire linkedin data in HTTP API body. I'm getting [object, Object] in request body not the actual data
What is teh right way to send the entire linkedin data in HTTP API body. I'm getting [object, Object] in request body not the actual data
To properly send LinkedIn data in the HTTP API body, you can: 1. Use the structured JSON inputs feature in HTTP API enrichments: • Go to "Add Enrichment" > select "HTTP API" • Enter your JSON objects directly or use formulas to generate them 2. For handling the entire LinkedIn profile data, use the "stringify" formula to convert the LinkedIn profile JSON into one cellIf you're still seeing [object, Object] in the request body, try these troubleshooting steps: ** Make sure all text values are in quotes ** Remove any trailing commas * Validate your JSON format using a tool like JSONLint Sources: FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? LinkedIn Profile Keyword lookup | Clay Find AI, Improved People Search, JSON Inputs, Weighted Round Robin, New Integrations, and more!
Was that helpful?
That doens't work if cell size is exceeded
To properly send the entire LinkedIn data in the HTTP API body: 1. Use the "stringify" formula to convert the entire LinkedIn profile JSON into one cell. This helps handle large amounts of LinkedIn profile data. 2. When formatting your JSON data, make sure to: • Put all text values in quotes • Remove any trailing commas • Validate your JSON format before sendingIf you're still experiencing issues, try using a JSON validator like JSONLint to check and fix your data format before sending it through the HTTP API. Sources: Find fundraising data from ZoomInfo | Clay FAQ: Why am I seeing the "failed to parse body" error when using the HTTP API enrichment? LinkedIn Profile Keyword lookup | Clay
Was that helpful?
Looks like you're still looking for help. If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!
Hi Parth, thanks for reaching out! Do you mind sending the link (url) to the table so we can take a look? https://downloads.intercomcdn.com/i/o/w28k1kwz/1347419411/65baf32e1d2a789ffba395c6d35c/CleanShot+2025-01-22+at+_42I1FzxXHf%402x.png?expires=1739302200&signature=40dee72cb11aecc758e56f895fdfd0a1837268bd1904e14e8463ea348704d1db&req=dSMjEc1%2FlIVeWPMW1HO4zVws4pg0DVaqgvYjA82bedC%2F%2BA%3D%3D%0A
Also i get this required field error even though it isn't required
Hey Parth, this is for the ClayDB API (2) column right?
correct
Do you have the API documentation for this endpoint?
its our own server
It looks like some rows have an error because the LinkedIn JSON Conversion formula column is blank https://downloads.intercomcdn.com/i/o/w28k1kwz/1376114760/ed12ae46cf4d8fd85592141195fa/CleanShot+2025-02-11+at+16_47_46%402x.png?expires=1739312100&signature=5aab6f55a704fb8d1e78de1666143ce6b5b5dd4a5bd06d1b64c51b5160a41a76&req=dSMgEMh%2FmYZZWfMW1HO4zcz0Usi6a30rOs04wnMjCoL1KE2OBLS2lPe4ppyl%0AmcxS%0A
So I've made this input optional in your Body but am still getting a body parse error, taking a look here
that is bc of cell limits. json stringify doesn't work when there's more data > cell limit
Trying to see if there is a workaround for this
What should the correct response look like? I fixed the body parse error and its returning 200 but there are no fields in the response
Take a look at the first 2 rows in this column for example
A workaround for the cell size limit is applying the same formula in an AI column. Enrichment fields don't have cell size limits, it's only when you add these fields as a column that it encounters the cell size limits
Unfortunately the linkedin data is required for us, so we can't make it not required in the payload. can u provide an example of the ai column
Hey Parth, I just created a "JSON Conversion" column at the end of your table. You can see that it returned the LinkedIn profile data as a JSON object with fields
Please check out the converted JSON array in the AI column output https://downloads.intercomcdn.com/i/o/w28k1kwz/1376152845/90df109d5d6f2fc621c96a6cb625/CleanShot+2025-02-11+at+17_20_09%402x.png?expires=1739313900&signature=9582fca0ccd1aa50855d0332264a06c505bae0da708a99047c622a297d8d85e5&req=dSMgEMh7n4lbXPMW1HO4zUnRCKlHRhN6k9yjFr277ULRajg2%2FvlfiL24jlQ5%0AFvLc%0A You can also link these fields in your HTTP API body https://downloads.intercomcdn.com/i/o/w28k1kwz/1376153149/f129f636701e82736c53764273d3/CleanShot+2025-02-11+at+17_20_24%402x.png?expires=1739313900&signature=b40271ae92784a163e3be1c060f0da6ce56731cd74b67e94d94e73a8644ba9b3&req=dSMgEMh7noBbUPMW1HO4zRRb1LvhONv2va1RjnHroWkRxLiLP%2Be8yix3g0Z3%0ADjiu%0A
Is there a more explicit way of doing this directly in the payload body? layering on GPT for this seems like it adds another point of failure / data integrity issue. Can we just call stringfy in the api call?
Hey Parth, we don't enable json formulas in the HTTP body directly unfortunately. The data needs to be manipulated in another column and then linked in the HTTP Body. In most cases a formula column would work here, it appears the input is just too large here to be in its own reference column
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.