Skip to main content

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

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

🔍 When You Don’t Have a Profile URL

Most of Enrich Layer’s endpoints are designed to enrich known profiles or companies — but what if you’re still looking for the right people?

That’s where the Person Search Endpoint comes in.

Instead of requiring a specific social profile URL, this API lets you search for people using filters like:

  • Job title or role (e.g., “product manager”)

  • Company or industry

  • Location

  • Education or experience level

It’s useful when you’re trying to:

  • Build a new list of prospects

  • Explore talent pools

  • Segment contacts for outreach or targeting

  • Power discovery tools inside your own product

What It Returns

Each search returns a list of potential matches with limited public info, such as:

  • Name, job title, company

  • Location (if available)

  • A social media profile link (in most cases)

From there, you can use the Person Search Endpoint to enrich specific results in more detail.

⚙️ Example Request (Simplified)

{

"current_role_title": "software engineer",

"region": "New York",

"page_size": 10

}

⚠️ Pagination may apply. Be mindful of result caps or rate limits based on your plan.

💳 How Credits Are Charged

Searches may be charged differently than enrichment calls. Depending on the setup, credits may be consumed:

  • Per page of results

  • Per returned profile

  • Or based on both filters and match depth

Check with your dashboard or support team if your usage isn’t clear.

✅ When to Use Person Search Endpoint

  • You want to build a lead list from scratch

  • You need to explore a talent market by title or region

  • You’re missing a social media URLs and want to locate them programmatically

🚫 When Not to Use It

If you already have a social media URL, use the Person Search Endpoint to enrich it directly.

If you’re looking for company data, try the Company API instead.


Did this answer your question?