Troubleshooting HTTP API Call Issues with Hunter.io Emails

Pedram M. · 2024-12-18T19:07:29.447Z

I'm having difficult sending a HTTP API call. I'm inserting all the "Find Emails by Company" from and selecting all properties, but my HTTP API end-point isn't receiving the "emails" key and value pair from the API.

Troubleshooting HTTP API Call Issues with Hunter.io Emails | Clay

Channeled
APP
·
·
Based on the Hunter API integration documentation, the output field is named "Emails" (with a capital 'E') and it returns an array type. Make sure you're using the exact field name "Emails" in your HTTP API call, as API fields are often case-sensitive. Source: Find Emails by Company with Hunter
Channeled
APP
·
·
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!
Pedram M.
·
·
{ "name": "Name", "domain": "Domain", "law_firm_status": "response", "emails": "Find Emails by Company" }
Pedram M.
·
·
This is the JSON body that I am sending w/ the Columns inserted. I'm using the Find Emails by Company and selecting all properties, but my HTTP api end-point doesn't receive the data
Bo (.
·
·
Pedram - Do you mind sending the link to the table so we can take a look? https://downloads.intercomcdn.com/i/o/1171717996/ac7729f84b426e1d0358af02/image.png?expires=1734551100&signature=6e691a40ce0010244245967352b80bbe999229d7e6ab5bc485418574d072e978&req=dSEgF85%2FmohWX%2FMW1HO4zYTywS%2F5A5YX2BKsam%2FhVPsVKw%3D%3D%0A
Pedram M.
·
·
https://app.clay.com/workspaces/432630/tables/t_5QGaFSArU3Wf/views/gv_q5PmqiKXQU47
Pedram M.
·
·
Could you please assist and help me Bo
Pedram M.
·
·
This is very critical to our work to send all the data points
Pedram M.
·
·
Are you there?
Pedram M.
·
·
Hello?
Bo (.
·
·
I can see why the data isn't coming through. 1. Your enrichment setup looks correct - The endpoint is returning a 500 error - The JSON structure you're sending matches the Find Emails enrichment output - The server is expecting the data in this specific format 2. Next steps: - We should check if the API endpoint is working properly - Verify the request payload format matches what the endpoint expects - Consider retrying the request after confirming the server is stable
Pedram M.
·
·
What's happening at row 16?
Pedram M.
·
·
It's saying an error message: "Failed to parse body input"
Bo (.
·
·
It had an issues with the quotation mark. Since you're adding an entire object the HTTP API was confused and was showing this error due to the extra quotes. I've went ahead and fixed the JSON structure directly using this: "{\n \"name\": \"" + Clay.formatForJSON({{Name}}) + "\",\n \"domain\": \"" + Clay.formatForJSON({{Domain}}) + "\",\n \"law_firm_status\": \"" + Clay.formatForJSON({{Law Firm Status}}?.response) + "\",\n \"emails\": " + JSON.stringify({{Find Emails by Company}}) + "\n}"
Pedram M.
·
·
Did you add a column?

48 comments