Person Contact Enrich - Crustdata Docs

Use this when you need contact data (business emails, personal emails, phone numbers) for a small number of people and want it back in the same request — for example, alongside full profile fields, or to reverse-look-up a person by their business email.

Choose this for a quick response. Contact data comes back in the same request for up to 25 identifiers. For a higher fill rate on bulk lists, use Batch Contact Enrich — an async job (typically a 2–3 minute wait).

POST https://api.crustdata.com/person/contact/enrich

Replace YOUR_API_KEY in each example with your actual API key. All requests require the x-api-version: 2025-11-01 header.

Availability: requires contact-enrich access (enterprise or higher-tier plans); self-serve keys receive a 403. Limits: up to 25 identifiers per request.

Contact endpoint rate limits are grouped with the live endpoints, not with in-database, so they do not move with the limits on search and enrich. See Rate limits.

Pricing

Billed per requested contact type, per matched person — there is no base credit, and only the types you request are fetched and billed.

Contact type requested	Credits per matched person
`contact.business_emails`	1
`contact.personal_emails`	2
`contact.phone_numbers`	2

Omitting fields requests all three (5, the maximum without verified). contact.websites is not one of the billed contact types, so requesting it currently uses 0 credits. Identifiers with no match are free. So is an identifier the person asked us to remove: it comes back with match_status: "redacted" and an empty matches. See Pricing for all endpoints. Set verified: true and each matched person who receives at least one verified business email costs 0.5 more. Business emails alone then cost 1.5 per matched person, and all three types cost 5.5. You pay nothing for the add-on on a person whose verified list comes back empty.

Enrich contact data

Request the contact field (or specific sub-fields) for one or more profile URLs.

curl --request POST \
  --url https://api.crustdata.com/person/contact/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"
    ],
    "fields": ["contact"]
  }'

[
    {
        "matched_on": "https://www.linkedin.com/in/abhilashchowdhary",
        "match_type": "professional_network_profile_url",
        "matches": [
            {
                "confidence_score": 1.0,
                "person_data": {
                    "contact": {
                        "business_emails": [
                            { "email": "abhilash@crustdata.com", "status": "deliverable" }
                        ],
                        "personal_emails": [
                            { "email": "personal@example.com", "status": "deliverable" }
                        ],
                        "phone_numbers": ["+1-555-0100"],
                        "websites": []
                    },
                    "crustdata_person_id": 1068035
                }
            }
        ]
    }
]

Email records are { email, status } objects, where status is one of deliverable, catch_all, invalid, or unknown (see Email status). The personal email and phone values above are illustrative.

Request only the sub-fields you need (for example contact.business_emails) to keep credit costs down. You can also combine contact with profile fields like basic_profile in the same request — see Person Enrich.

Contact fields

Field	Returns
`contact`	All contact records: emails, phone numbers, websites
`contact.business_emails`	Business email records
`contact.personal_emails`	Personal email records
`contact.phone_numbers`	Phone numbers
`contact.websites`	Personal or company-linked websites

Email status

Every business and personal email comes back with a status that tells you how deliverable the address is. Use it to decide which emails to send to.

Status	Meaning
`deliverable`	The mailbox was confirmed to exist and accept mail at this exact address. Lowest bounce risk.
`catch_all`	The domain accepts mail for any address, so this specific mailbox can’t be confirmed. It may work, but delivery isn’t guaranteed.
`invalid`	The mailbox was confirmed not to exist or is otherwise undeliverable. Sending will bounce.
`unknown`	Deliverability couldn’t be determined (for example a timeout or an inconclusive check). Returned when no status info is available.

Verified business emails only

Set verified: true to get back only business emails that pass a deliverability check at request time. Crustdata re-checks cached addresses marked deliverable or unknown before serving them and drops any address that fails. The response then holds only deliverable and catch_all business emails. Personal emails and phone numbers do not change.

curl --request POST \
  --url https://api.crustdata.com/person/contact/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"
    ],
    "fields": ["contact.business_emails"],
    "verified": true
  }'

[
    {
        "matched_on": "https://www.linkedin.com/in/abhilashchowdhary",
        "match_type": "professional_network_profile_url",
        "matches": [
            {
                "confidence_score": 1.0,
                "person_data": {
                    "contact": {
                        "business_emails": [
                            { "email": "abhilash@crustdata.com", "status": "deliverable" }
                        ]
                    },
                    "crustdata_person_id": 1068035
                }
            }
        ]
    }
]

[
    {
        "matched_on": "https://www.linkedin.com/in/example-profile",
        "match_type": "professional_network_profile_url",
        "matches": [
            {
                "confidence_score": 1.0,
                "person_data": {
                    "contact": {
                        "business_emails": [],
                        "business_emails_message": "no verified emails found"
                    },
                    "crustdata_person_id": 12345
                }
            }
        ]
    }
]

When no address survives the check, business_emails is an empty array and business_emails_message reads no verified emails found. The person still counts as matched, but you pay nothing for business emails. The second response above is illustrative.

verified only changes contact.business_emails. It has no effect unless you request business emails, and it adds 0.5 credits per matched person who receives at least one verified business email. The check runs at request time, so expect a slower response than an unverified call.

Get a specific contact type

Request a single sub-field to return only that contact type — useful for keeping credit costs down. This endpoint always returns contact only (no profile fields like basic_profile or experience).

Business emails only — 1 credit

curl --request POST \
  --url https://api.crustdata.com/person/contact/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"],
    "fields": ["contact.business_emails"]
  }'

Returns only the contact.business_emails array — no other contact fields or profile data. Billed 1 credit per matched person.

Personal emails only — 2 credits

curl --request POST \
  --url https://api.crustdata.com/person/contact/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"],
    "fields": ["contact.personal_emails"]
  }'

Returns only the contact.personal_emails array. Billed 2 credits per matched person.

Phone numbers only — 2 credits

curl --request POST \
  --url https://api.crustdata.com/person/contact/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"],
    "fields": ["contact.phone_numbers"]
  }'

Returns only the contact.phone_numbers array. Billed 2 credits per matched person.

Reverse lookup by business email

Pass business_emails instead of profile URLs — the endpoint resolves each email to its person and returns their contact data in the same request. No separate identification call is needed.

curl --request POST \
  --url https://api.crustdata.com/person/contact/enrich \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "business_emails": ["abhilash@crustdata.com"],
    "fields": ["contact.business_emails"]
  }'

[
    {
        "matched_on": "abhilash@crustdata.com",
        "match_type": "business_email",
        "matches": [
            {
                "confidence_score": 1.0,
                "person_data": {
                    "contact": {
                        "business_emails": [
                            { "email": "abhilash@crustdata.co", "status": "deliverable" },
                            { "email": "abhilash@crustdata.com", "status": "deliverable" }
                        ]
                    }
                }
            }
        ]
    }
]

Use exactly one identifier type per request — business_emails and professional_network_profile_urls cannot be mixed in the same call. If you only need to know who owns an email (identity, not contact data), use Identify (Reverse Email Lookup).

Request parameters

Parameter	Type	Required	Description
`professional_network_profile_urls`	string[]	One of these two identifiers	Profile URLs to enrich. Max 25.
`business_emails`	string[]	One of these two identifiers	Business emails for reverse lookup. Max 25.
`fields`	string[]	No	Which fields to return. Use `contact` (or its sub-fields).
`verified`	boolean	No	Return only business emails that pass a deliverability check at request time. Default `false`. Adds 0.5 credits per matched person who receives a verified business email. See Verified business emails only.

Errors

Status	Meaning
`400`	Invalid request — malformed identifier or missing one.
`401`	Invalid or missing API key.
`403`	Permission denied or insufficient credits.
`500`	Internal server error. Retry with exponential backoff.

API reference summary

Detail	Value
Endpoint	`POST /person/contact/enrich`
Auth	Bearer token + `x-api-version: 2025-11-01`
Request	One of `professional_network_profile_urls` or `business_emails` (max 25). `fields`: `contact`. Optional `verified`.
Response	Array: `[{ "matched_on", "match_type", "match_status", "matches": [{ "confidence_score", "person_data" }] }]`.
Errors	`400`, `401`, `403`, `500`

For the full field catalog and identifier behavior, see the Person Enrich reference. For credit pricing, see Pricing.

What to do next

Enrich in bulk — Batch Contact Enrich handles large lists asynchronously with no per-profile base fee.
Get full profiles — Person Enrich returns profile, employment, and education data.
Find people first — use Person Search to build your list of profile URLs.

​Pricing

​Enrich contact data

​Contact fields

​Email status

​Verified business emails only

​Get a specific contact type

​Request parameters

​Errors

​API reference summary

​What to do next

Pricing

Enrich contact data

Contact fields

Email status

Verified business emails only

Get a specific contact type

Request parameters

Errors

API reference summary

What to do next