- What does one call return?
- One public profile as JSON: identity, headline, about, location, experience, education, followers, connections, creator badges, the latest posts and articles, and scraped_at. Every key is always present; a value the profile does not show is null, an empty list is [].
- How fresh is the data?
- Every call fetches the profile live at request time. Nothing is cached, and scraped_at tells you exactly when it was read.
- What am I charged for?
- 1 credit per profile returned. Profiles that are not found, private, or not served by LinkedIn at that moment are refunded automatically, and so are timeouts.
- Do I need a LinkedIn account or cookies?
- No. ProfileHunt reads only what a logged-out visitor can see. Your LinkedIn account is never involved.
- Is this the full LinkedIn profile?
- No. It is the public view: what anyone sees on LinkedIn without signing in. Anything a member shows only to signed-in users, such as contact details, exact connection counts above 500 or hidden roles, is not included.
- Why are some fields null?
- LinkedIn hides some details from logged-out visitors for many members, for example job titles or older roles. We return null instead of guessing, so what you get is what the profile shows publicly.
- How are dates formatted?
- Role and school dates are strings as LinkedIn shows them: "2014" or "2014-02". Post and scrape times are ISO 8601 timestamps in UTC.
- Can I use it from Clay, n8n or my own code?
- Yes. It is one HTTPS POST with a bearer key, so any HTTP step works: Clay's HTTP API column, n8n's HTTP Request node, or a few lines of Python or Node.