Empty or Missing Fields in Responses
Why some fields return null and how to get more complete data.
It's common for some fields in API responses to be null or missing. This isn't an error — it means the data isn't available from the source.
Why fields are empty
- The person hasn't listed it — Not everyone lists their email, phone number, or all job history on their profile
- Privacy settings — Some people restrict what's visible on their profiles
- Data source limitations — Some data points require additional lookups
Getting more data
Include optional fields
Many endpoints have optional data fields that aren't included by default. Add them explicitly:
curl -G \
-H "Authorization: Bearer YOUR_API_KEY" \
'https://enrichlayer.com/api/v2/profile' \
--data-urlencode 'profile_url=https://linkedin.com/in/someone/' \
--data-urlencode 'skills=include' \
--data-urlencode 'personal_email=include' \
--data-urlencode 'personal_contact_number=include' \
--data-urlencode 'twitter_profile_id=include' \
--data-urlencode 'facebook_profile_id=include' \
--data-urlencode 'github_profile_id=include' \
--data-urlencode 'extra=include'bash
Force a fresh lookup
Cached results may be stale. Try a fresh lookup:
live_fetch=forcetext
Expected fill rates
Not every field will be populated for every person. Typical fill rates:
| Field | Fill rate |
|---|---|
| Full name | ~99% |
| Headline / current title | ~95% |
| Location (city/country) | ~90% |
| Work experience | ~85% |
| Education | ~75% |
| Personal email | ~40-60% |
| Phone number | ~20-40% |
| Social media profiles | ~30-50% |