Troubleshooting HTTP API Setup Issues with Forager Clay Partner

Daniel T. · 2026-01-16T16:26:48.166Z

I wanted to setup an http API and it keeps showing me errors. The native API connection did also not work. It is about Forager which is a Clay partner. Any advise?

Troubleshooting HTTP API Setup Issues with Forager Clay Partner | Clay

Muhammad S.
·
·
can you share errors?
Clay Support
APP
·
·
To help troubleshoot your HTTP API setup with Forager, I'll need to see the specific error messages you're getting. [1]
Can you copy and paste the exact error messages into the chat? Also, click into the specific cells where you're seeing errors to get more detailed error information.
Common HTTP API errors include "failed to parse body" (usually JSON formatting issues) or authentication problems. [2] Once I see your errors, I can guide you through the specific fixes needed. [3]
Daniel T.
·
·
The integration failed to run Clay received a 400 error from the API with Content: {“non_field_errors”:[“No person identifier has been provided.“]}
Daniel T.
·
·
I used the linkedin url of the person though as an identifier
Clay Support
APP
·
·
The error "No person identifier has been provided" means Forager needs a required input field that's missing or empty. [1]
For Forager integrations, you need to provide:
Professional URL for finding phone numbers or personal emails
Personal email for finding professional profiles [2]
Check that your input column isn't empty and contains the correct data type. Click into the specific error cell to see more details about what's missing.
Can you paste your current JSON body configuration so I can help troubleshoot the exact issue?
Muhammad S.
·
·
you need to pass in the linkedin url of the person in the input, can you share your http api body here?
Clay Support
APP
·
·
For Forager's HTTP API, you need to structure your JSON body correctly. The field name should be "professional_url" (not just "url" or "linkedin_url"). [1]
Your JSON body should look like:
{ "professional_url": "/LinkedIn URL Column" }
Can you paste your current HTTP API body so I can see exactly what's causing the "No person identifier" error? This will help me spot any formatting issues. [2]
Daniel T.
·
·
i did. { “linkedin_url”: ” ” }
Daniel T.
·
·
i put the right column in there
Clay Support
APP
·
·
I see the issue! You're using "linkedin_url" but Forager expects "professional_url" as the field name. [1]
Also, your JSON has quotes around empty spaces - make sure you're referencing your actual LinkedIn column like this:
{ "professional_url": "/Your LinkedIn Column Name" }
The column reference needs quotes around it for string values. [2] Can you update it with the correct field name and your actual column reference?
Clay Support
APP
·
·
The issue is that Forager expects "professional_url" as the field name, not "linkedin_url". [1]
Change your JSON body to:
{ "professional_url": "/Your LinkedIn Column" }
Also make sure there are no extra spaces in your column reference - it should be exactly /Column Name with quotes around it. [2]
Clay Support
APP
·
·
Was that helpful?

Muhammad S.

use this: Daniel T.

{ "linkedin_public_identifier": "" }

instead of

{ "linkedin_url": "" }

Clay Support
APP
·
·
Got it! You're right - for Forager's HTTP API, use "linkedin_public_identifier" instead of "linkedin_url". [1]
Your JSON should be:
{ "linkedin_public_identifier": "/Your LinkedIn Column" }
Make sure to include quotes around your column reference for string values. [2] This should resolve the "No person identifier" error you were getting.
Clay Support
APP
·
·
Was that helpful?

17 comments