Troubleshooting Serper.dev 400 Error for LinkedIn Webpage Scraping

hanad canter · 2025-02-20 20:17:35.419345+00

Does anyone know how to get around status 400 error. It's saying i have the wrong URL parameters but it works in but not clay. I'm trying to do a linkedin webpage scrape.

Troubleshooting Serper.dev 400 Error for LinkedIn Webpage Scraping | Clay

Channeled
APP
·
·
To resolve the status 400 error when scraping LinkedIn webpages in Clay, ensure you're using the correct URL format and method. For LinkedIn profile scraping, use our integration with Sales Navigator: 1. Go to Method Filter > Select External List 2. Paste your Sales Navigator search URL in the Query section 3. Use full URLs, including https:// (e.g., https://www.linkedin.com/in/username/) Note: LinkedIn Sales Navigator links aren't supported for direct scraping. If you're using the Clay Chrome Extension, make sure you're on the correct page and using the "Select Data to Add from Page" feature.
Sources: Clay Chrome extension | Documentation | Clay University Clay enrichments integration overview | Documentation | Clay University
Channeled
APP
·
·
Was that helpful?
Muhammad
·
·
what is issue
Muhammad
·
·
can you show your serper.dev inputs in clay?
Muhammad
·
·
a screenshot?
Channeled
APP
·
·
The status 400 error when scraping LinkedIn webpages in Clay is likely due to incorrect URL parameters. To resolve this issue: 1. Use our Sales Navigator integration instead of direct LinkedIn scraping. 2. Go to Method Filter > Select External List. 3. Paste your Sales Navigator search URL in the Query section. 4. Ensure you're using full URLs, including https://. Note that Clay doesn't connect directly to LinkedIn accounts and relies on public web scraping. If you need additional data, consider using Claygent, our built-in AI research tool with web access, for best results.
Channeled
APP
·
·
Was that helpful?
Channeled
APP
·
·
I apologize, but I can't provide a screenshot directly. However, I can guide you on setting up the Serper integration in Clay: 1. Create a Serper.dev account and get your API key. 2. In Clay, set up an HTTP API call column. 3. Use the following parameters in your column setup: • Endpoint: [Your Serper endpoint] • API key: [Your Serper API key] (in the header) • Headers: As specified in Serper's cURL structure • JSON body: Copy from Serper's cURL example Remember to compile your Google query using a formula, as only one dynamic token can be input in the API body. For more detailed instructions, you can check our integration guide for Serper on the Clay website.
Source: Scrape Search Results with Serper | Clay.com
Channeled
APP
·
·
Was that helpful?
hanad canter
·
·
Loading attachments
Channeled
APP
·
·
To set up and use Serper.dev inputs in Clay for your integration, follow these steps: 1. Create a Serper.dev account and obtain your API key. 2. In Clay, set up an HTTP API call column. This requires an Explorer plan or higher. 3. Configure your HTTP API call column with the following parameters: • Endpoint: Use your Serper endpoint • API key: Include your Serper API key in the header • Headers: Copy from Serper's cURL structure • JSON body: Use the structure from Serper's cURL example 4. When setting up your query, compile it using a formula. Note that only one dynamic token can be input in the API body. 5. In the "Configure" section of the enrichment side panel, provide the required input parameters for your Serper integration. 6. Use the "Define Outputs" section to specify how you want the response formatted, either as individual fields or in a JSON schema. For more detailed instructions, refer to Clay's integration guide for Serper on their website.
Source: Run an enrichment | Documentation | Clay University
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!
hanad canter
·
·
Muhammad
Muhammad
·
·
can you show me values in NEW COLUMN? maybe copy paste one here?

41 comments