SupportFor Solutions
Pull your leads into Salesforce, a warehouse or any tool with an API key.
Create an API key on your Pipeline page (Manage Integrations, then API Endpoint, then Create key), copy it once, and call GET https://humancloud.com/api/solutions/your-solution-id/leads with the header Authorization: Bearer your-key. Add ?since= with the time of your last pull to get only new leads. Every lead says how we know who it is.
https://humancloud.com/solution-dashboard/your-profile/leads, then Manage Integrations, then the API Endpoint card. Your endpoint URL, with your solution id, is shown there.In the API Endpoint card, name the key (for example "Salesforce daily job") and click Create key. Copy it right away: it's shown once. We store only a fingerprint of it, so nobody can view it again, us included. Keep it in a secret store such as an encrypted CI variable or Salesforce named credentials.
curl -H "Authorization: Bearer hc_live_..." "https://humancloud.com/api/solutions/your-solution-id/leads?since=2026-11-01T00:00:00Z"
Options: since (an ISO time; only leads after it), limit (default 50, up to 200), offset, format=csv for CSV, and kind=scored for matched prospects only.
Save the time of each pull and pass it as since next time. Use the lead's email as the match key in your CRM; our id identifies the activity, not the person. Keys are limited to 60 requests a minute.
kind: scored (a prospect matched to your ICP) or visitor (someone who viewed your profile).identifiedVia: how we know who it is. icp_prospect (matched from Human Cloud's network), signed_in (they have a Human Cloud account), enriched (named by visitor identification) or company_only (we know the company, not the person).companyOnly: true when we know the company but not the person.name, title, email, linkedinUrl, companyName, companyDomain.score and scoreFactors for matched prospects; intent for visitors.surfacedAt: when the lead was added or the visit happened.Your own team is never included.
The key is missing, mistyped or revoked. Send it exactly as Authorization: Bearer hc_live_..., or create a new key.
The key belongs to a different solution than the one in the URL. Use the endpoint URL shown next to the key.
More than 60 requests in a minute. Wait for the number of seconds in the Retry-After header.
Create a new key, switch your job to it, then click Revoke on the old one. A revoked key stops working at once.