Skip to main content

How the Person Profile Endpoint Works — and When to Use It

Freddy Rodriguez avatar
Written by Freddy Rodriguez
Updated over 2 months ago

👋 Meet the Person Profile Endpoint

The Person Profile Endpoint lets you access detailed information about individuals based on a known public profile URL (e.g., a professional or social media profile).

It’s designed for 1:1 enrichment, meaning you provide a direct profile link and get structured data about that person in return. It’s ideal for B2B enrichment, lead validation, talent mapping, and more.

What You Can Get From It

A successful Person Profile Endpoint call can return:

  • Full name, headline, and job title

  • Company and role details

  • Work history, education, and skills

  • Optional enrichments like:

    • certifications

    • projects

    • publications

Just like with the Company Profile Endpoint, you can choose to exclude additional data to reduce credit usage.

⚙️ How It Works

To use the Person Profile Endpoint, you’ll need:

  • A valid social media profile URL

You’ll send a POST request to the Person Profile Endpoint with the URL as the main input.

Example:

{

}

If you don’t include optional enrichments, the default response will return core information only.

How Credits Are Used

A basic Person Profile Endpoint call typically costs 1 credit.

You may be charged 2 or more credits if:

  • data freshness is enabled (use_cache=if-recent)

  • You include enrichments that require deeper data lookups

✅ When to Use the Person Search Endpoint

  • Enriching leads in your CRM

  • Pulling profile data for personalized outreach

  • Verifying job history or current position

  • Building user segments based on industry, education, or company


Want to Try It?

You can test the endpoint using Postman, curl, or a no-code API tool. Just remember—if the profile doesn’t exist or can’t be found, no credits will be deducted.

⚠️ Looking for a different use case? We’ll be adding more endpoint guides soon. Let us know what you’d like covered next!


Did this answer your question?