> ## Documentation Index
> Fetch the complete documentation index at: https://deepline.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Crustdata People Enrich: Inputs, Cost & CLI Example
> Enriching multiple people records in batch style. Includes inputs, outputs, pricing notes, Deepline CLI examples, and GTM automation guidance.
## Run in Enrichment Spreadsheet
Use this function as a column step in `deepline enrich`.
```bash theme={null}
deepline enrich --input leads.csv --output leads.enriched.csv --with 'result=crustdata_people_enrich:{"linkedinProfileUrl":"https://www.linkedin.com/in/example"}' --json
```
Map payload values to spreadsheet columns with `{{column_name}}` placeholders.
## Input Schema
| Name | Type | Required | Default | Description |
| ---------------------------- | ----------------- | -------- | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `payload.linkedinProfileUrl` | `string \| array` | No | | LinkedIn profile URL(s) to enrich. This is the default profile lookup path. |
| `payload.businessEmail` | `string \| array` | No | | Business email lookup input. Use this instead of linkedinProfileUrl to find a profile by email. This is different from requesting business\_email in fields. |
| `payload.fields` | `string \| array` | No | | Fields to return (array or comma-separated). Contact fields change the per-profile price: business\_email/businessEmail, personal\_contact\_info.personal\_emails/personal\_emails, and personal\_contact\_info.phone\_numbers/phone\_numbers are paid add-ons. business\_email is not charged twice when businessEmail is already the lookup input. |
| `payload.enrichRealtime` | `boolean` | No | `false` | Trigger realtime enrichment. Uses the realtime per-profile price. Default false; never recommend unless the user explicitly asks for realtime enrichment. |
Show raw input schema
### Input JSON Schema
```json theme={null}
{
"type": "object",
"description": "Looks up a person by LinkedIn URL or business email using /screener/person/enrich. Priced per returned profile.",
"properties": {
"linkedinProfileUrl": {
"description": "LinkedIn profile URL(s) to enrich. This is the default profile lookup path.",
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"type": "string",
"minLength": 1
}
}
]
},
"businessEmail": {
"description": "Business email lookup input. Use this instead of linkedinProfileUrl to find a profile by email. This is different from requesting business_email in fields.",
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"type": "string",
"minLength": 1
}
}
]
},
"fields": {
"description": "Fields to return (array or comma-separated). Contact fields change the per-profile price: business_email/businessEmail, personal_contact_info.personal_emails/personal_emails, and personal_contact_info.phone_numbers/phone_numbers are paid add-ons. business_email is not charged twice when businessEmail is already the lookup input.",
"anyOf": [
{
"type": "string",
"minLength": 1
},
{
"type": "array",
"minItems": 1,
"items": {
"type": "string",
"minLength": 1
}
}
]
},
"enrichRealtime": {
"type": "boolean",
"description": "Trigger realtime enrichment. Uses the realtime per-profile price. Default false; never recommend unless the user explicitly asks for realtime enrichment.",
"default": false
}
},
"additionalProperties": false
}
```
## Output Schema
| Name | Type | Required | Default | Description |
| ------------- | -------- | -------- | ------- | ---------------------------------------------- |
| `result.data` | `array` | Yes | | Provider response payload. |
| `result.meta` | `record` | No | | Additional response metadata (status, paging). |
Show raw output schema
### Output JSON Schema
```json theme={null}
{
"type": "object",
"description": "Crustdata people enrich result.",
"properties": {
"data": {
"type": [
"array",
"null"
],
"description": "Provider response payload.",
"items": {
"type": "object",
"additionalProperties": {}
}
},
"meta": {
"type": "object",
"description": "Additional response metadata (status, paging).",
"additionalProperties": {}
}
},
"required": [
"data"
],
"additionalProperties": false
}
```
## Advanced: Direct CLI
Use direct execution for single payload debugging.
```bash theme={null}
deepline tools execute crustdata_people_enrich --payload '{
"linkedinProfileUrl": "https://www.linkedin.com/in/example"
}' --json
```
### CLI flags
| Flag | Description |
| --------------------------- | --------------------------------------------------- |
| `--json` | Print machine-readable output. |
| `--wait` | Wait for terminal provider status when supported. |
| `--debug` | Enable wait mode with additional status/log output. |
| `--wait-timeout SECONDS` | Max seconds to wait in wait mode. |
| `--poll-interval SECONDS` | Polling interval in seconds during wait mode. |
| `--timeout SECONDS` | Request timeout in seconds. |
| `--connect-timeout SECONDS` | Connection timeout in seconds. |
## Provider API Context
Show provider reference (optional)
````md theme={null}
### [ 🚀 Try Now ](https://docs.crustdata.com/api#tag/people-apis/GET/screener/person/enrich) This API allows you to retrieve enriched data for one or more LinkedIn profiles in a single request. ## Endpoint ``` GET /screener/person/enrich ``` ## Data Dictionary [People Enrichment API Data Dictionary](https://docs.crustdata.com/docs/2024-11-01/dictionary/people-enrichment) ## Request Parameters | Parameter | Type | Required | Default | Description | Example| |-----------|------|-------|---------|-------------------| -----| | `linkedin_profile_url` | string | Yes | — | Comma-separated list of LinkedIn profile URLs (25 max limit) of the person to enrich | `https://www.linkedin.com/in/dvdhsu/`,<br></br>`https://www.linkedin.com/in/jonnilundy/` | | `enrich_realtime` | boolean | No | `false` | Whether to enrich the profile in real-time | `true` | | `business_email` | string | No | — | Business email of the person to enrich | `abhilash@crustdata.com` | | `fields` | string | No | - | Specify the fields to include in the response | `all_degrees,education_background` | | `preview` | boolean | No | `false` | [**Access controlled**] <br/>Provides basic profile details lookup | `true` | <details id="mapping-multiple-profiles"> <summary><strong>Mapping Multiple LinkedIn URLs to Response Objects</strong></summary> When providing multiple LinkedIn URLs, each response object includes a **`query_linkedin_profile_urn_or_slug`** field containing the profile slug (the part after `/in/` in the URL) to identify which input URL it corresponds to. **Example:** Request `linkedin_profile_url=https://www.linkedin.com/in/siqic,https://www.linkedin.com/in/neelesh-soni` returns: ```json [ {"name": "Siqi Chen", "query_linkedin_profile_urn_or_slug": ["siqic"]}, {"name": "Neelesh Soni", "query_linkedin_profile_urn_or_slug": ["neelesh-soni"]} ] ``` </details> #### Key Features - Latency - **Database Search:** Less than **10 seconds** per profile. - **Real-Time Search:** May take longer due to fetching data from the web. - Limits - **Profiles/Emails per Request:** Up to **25**. - **Exceeding Limits:** Requests exceeding this limit will be rejected with an error message. - Constraints - **Valid Input:** Ensure all LinkedIn URLs and email addresses are correctly formatted. - Invalid inputs result in validation errors. - **Mutually Exclusive Parameters:** Do not include both linkedin_profile_url and business_email in the same request. - **Independent Processing:** Each profile or email is processed independently. - Found entries are returned immediately - Not found entries trigger the enrichment process (if enrich_realtime=False) :::info ##### Business Email Enrichment - **Discovery:** Discover business email addresses of professionals based on their LinkedIn profiles. - **Implementation:** To enable, include `business_email` in the `fields` parameter: ``` GET /screener/person/enrich?linkedin_profile_url=https://www.linkedin.com/in/example&fields=business_email ``` ::: ## Credit Usage - **Database Enrichment:** - **3 credits** per LinkedIn profile or email. - **Real-Time Enrichment (enrich_realtime=True):** - **5 credits** per LinkedIn profile or email. - **Email Enrichment:** - **2 additional credits** when requesting business email - **Preview Mode:** - **0 credits** when `preview=true` is used - **No Results, No Charges**: You are never charged credits when our APIs return no results. Credits are only deducted when data is successfully returned from your API requests. ## Example Requests <details id="1-get-all-fields-example"> <summary>1. Get all fields example</summary> ### 1. Get all fields example - Usecase: Retrieve comprehensive profile data including all available fields for a single LinkedIn profile ```bash curl --location 'https://api.crustdata.com/screener/person/enrich?fields=linkedin_profile_url,linkedin_flagship_url,name,location,email,title,last_updated,headline,summary,num_of_connections,skills,profile_picture_url,profile_picture_permalink,twitter_handle,languages,all_employers,past_employers,current_employers,education_background,all_employers_company_id,all_titles,all_schools,all_degrees&linkedin_profile_url=https://www.linkedin.com/in/manmohitgrewal/' \ --header 'Authorization: Token $auth' \ --header 'Accept: application/json, text/plain, */*' \ --header 'Content-Type: application/json' ``` </details> <details id="2-real-time-enrichment"> <summary>2. Real-time enrichment</summary> ### 2. Real-time enrichment - Usecase: Ideal for users who wants to enrich a profile in realtime from LinkedIn ```bash curl -X GET "https://api.crustdata.com/screener/person/enrich?linkedin_profile_url=https://www.linkedin.com/in/abhilashchowdhary&enrich_realtime=true" \ -H "Authorization: Token auth_token" \ -H "Accept: application/json, text/plain, */*" \ -H "Content-Type: application/json" ``` </details> <details id="3-request-for-business-email-and-all-default-fields"> <summary>3. Request with business email enrichment</summary> ### 3. Request for business email and all default fields :::info 1. Only email enrichment - If you only request for `fields=business_email`, the endpoint will return just the email—no default profile fields (name, location, LinkedIn URL, headline, etc.). - This keeps the call cheap: 2 credits for email enrichment. 2. Email enrichment with profile enrichment - If you want to get the profile details along with business email you can add them to fields param in the request as shown in this example. - Cost: 2 credits for the email + 3 credits for profile enrichment (5 if realtime=true). ::: ```bash curl -X GET
<Note>
Provider reference truncated for page speed. Use the provider's official docs for the full upstream reference.
</Note>
````
## Cost
* Pricing model: `per_result` (per result).
* Estimated Deepline credits: `0.4` per pricing unit.
* Billing mode: `post_deduct`.