Skip to main content
The Person Enrich API takes an identifier you already have — a profile URL or a business email — and returns a rich person profile. This page walks you through the basics: your first enrichment, the response shape, and the person_data sections. For deeper topics, follow the links to the sub-pages. Every request goes to the same endpoint: 
POST https://api.crustdata.com/person/enrich
Replace YOUR_API_KEY in each example with your actual API key. All requests require the x-api-version: 2025-11-01 header.

​
Request body

ParameterTypeRequiredDescription
professional_network_profile_urls / business_emailsarrayYes — one onlySubmit exactly one identifier type. Max 25 per request.
fieldsarrayNoSpecific field paths or section groups to include.
min_similarity_scorenumberNoMinimum confidence threshold for email reverse lookup.
force_fetch / enrich_realtimeboolNoAdvanced refresh flags (see Reference).

​
Response body

The response is a top-level array. Each entry corresponds to one input identifier.
FieldTypeDescription
matched_onstringThe input identifier (profile URL or email)
match_typestringprofessional_network_profile_url or business_email
matchesarrayCandidate matches. Empty for no-match inputs.
matches[].confidence_scorenumber0 to 1. Higher is better. 1.0 is common for direct URL lookups.
matches[].person_dataobjectFull enriched profile.

​
Rate limits and pricing

Pricing: Base profile is 1 credit. Add +2 for personal email, +2 for phone, +1 for business email, and +1 for developer platform data. Maximum: 7 credits per profile.

Identifiers

Email reverse lookup, batch enrichment, no-match handling, Search → Enrich workflow.

Reference

Request parameters, response fields, valid fields values, person_data sections, advanced flags, errors.

​
Your first enrichment: look up a profile

The simplest enrichment takes a single profile URL and returns the person’s cached profile. Pass the URL in the professional_network_profile_urls array. 
curl --request POST \
  --url https://api.crustdata.com/person/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "professional_network_profile_urls": [
      "https://www.linkedin.com/in/abhilashchowdhary/"
    ]
  }'
Response trimmed for clarity. The full response can include employment history, education, skills, contact data, and developer platform profiles when available.

​
Understanding the response

The Enrich API returns an array — one entry per identifier you submitted. Each entry has three fields:
  • matched_on — the identifier you submitted (a profile URL or email).
  • match_type — either professional_network_profile_url or business_email, telling you which identifier type was used.
  • matches — an array of candidate profiles. Each match includes a confidence_score (0 to 1) and the full person_data object.
For profile URL lookups, you will typically get exactly one match with a confidence_score of 1.0, because the URL is a direct identifier.

​
Need fresh data from the web?

If the cached enrich response is missing a recent update or you need real-time retrieval from the web, use Person Live Enrich. That endpoint is designed for fresh profile retrieval when cached enrich is not enough.

​
What to do next

  • Enrich by email or in batch — see Identifiers for business-email reverse lookups, multi-profile requests, and workflows.
  • Request only the sections you need — see Using the fields parameter to reduce response size.
  • Look up request/response details — see Enrich reference.
  • Search first, then enrich — use Person Search to find people by name, title, company, or location, then enrich the results.
  • Fetch fresh data from the web — use Person Live Enrich when cached enrich is not enough.
  • Read the overview — see Person Search for the main Search entry point.