Testing Serper Dev on Clay: Need Help Troubleshooting Issues

If you're encountering an issue when testing Serper Dev on Clay, common causes include incorrect JSON formatting or setup issues with the HTTP API integration. Double-check that your JSON body is properly formatted—ensure all keys and string values use double quotes, commas are placed correctly between key-value pairs, and brackets/braces are matched. A "failed to parse body" error often points to these formatting problems. Additionally, make sure you have an Explorer plan, as Serper integration requires it. You need to use your Serper API key in the HTTP API call setup, placing it in the header, and structure your request body according to the cURL example from Serper's documentation. Only a single dynamic token can be used in the API body. If you can share the exact JSON or error message, I can help troubleshoot further. Please copy and paste the JSON here for more specific guidance.

Sources: Scrape Search Results with Serper | Clay.com Extract a list of companies that can't be filtered for on Apollo or scraped from Google Maps | Clay Claybooks: Turn Google Maps listings into a target account list with contacts and emails | Clay.com