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

26 comments

· Sorted by Oldest

Channeled
APP
·
·
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!
Channeled
APP
·
·
Was that helpful?
Parth P.
·
·
That doens't work if cell size is exceeded
Channeled
APP
·
·
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
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
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!
Tanvi R.
·
·
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
Parth P.
·
·
https://app.clay.com/workspaces/4711/workbooks/wb_ARSCjHdYWhzF/tables/t_79qM9ei7inCm/views/gv_Wk7jYHhTjNM9
Parth P.
·
·
Also i get this required field error even though it isn't required
Loading attachments
Tanvi R.
·
·
Hey Parth, this is for the ClayDB API (2) column right?
Parth P.
·
·
correct
Tanvi R.
·
·
Do you have the API documentation for this endpoint?
Parth P.
·
·
its our own server
Tanvi R.
·
·
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
Tanvi R.
·
·
So I've made this input optional in your Body but am still getting a body parse error, taking a look here