Using the enrich_profile=enrichparameter in your API request lets you access more extensive profile data. Just note that this may come with an additional credit cost.
This guide explains what it does, when to use it, and how it can impact your usage.
What Is enrich_profiles?
The enrich_profiles parameter is used in some API requests to enrich the profiles returned by your query. When enabled, this setting pulls in additional data fields, such as:
Job title and company
Work history
Education
It allows you to turn a basic match (like a public profile URL or domain) into a fully enriched profile—all in one request.
Does It Affect Credit Usage?
Yes. Enabling the enrich_profiles=enrich parameter can increase the total number of credits used per result. That’s because enrichment pulls in more detailed data and may use separate endpoints behind the scenes.
Note: This usually adds 1 extra credit per profile, depending on the endpoint you’re using.
When Should I Use It?
Use the enrich_profiles=enrich parameter when you want more than just basic profile data of a person or a company—and you need rich, structured data to power things like:
Lead scoring or routing
CRM enrichment
Recruiting insights
Persona development
If you’re just testing or trying to minimize credit usage, you might want to leave this off and enrich selected profiles later.
⚙️ Example Usage
{
"query": {
"role": "engineer",
"location": "San Francisco"
},
"page_size": 10,
"enrich_profiles": enrich
}
This request searches for profiles and enriches each result automatically.
📌 A Few Things to Keep in Mind
enrich_profiles enhances returned records with more data fields.
It’s optional but adds value for production use cases.
Enabling it may increase your credit consumption.
Use it when you need enriched records right away—skip it for lightweight tests.
Still Have Questions?
👉 Not sure if this setting is right for you?
Just click the chat icon in the bottom-right corner — we’ll walk you through it.