Enrichment
Enrich a known LinkedIn identity with selected profile or contact fields.
Focused person enrichment
POST /v1/enrichRequires people:enrich and a LinkedIn profile URL.
curl https://api.ploid.com/v1/enrich \
-H "Authorization: Bearer $PLOID_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"linkedin_url": "https://www.linkedin.com/in/example",
"first_name": "Example",
"last_name": "Person",
"enrichments": ["profile", "email", "phone"],
"response_format": "standard"
}'Allowed enrichment names are profile, email, and phone. Ask only for fields the application needs.
Partial success
One field can fail without failing the whole person. Unresolved fields return null, and transport or provider failures appear in meta.warnings. Clean not-found fields and failed fields are not charged.
Identity first
Use the strongest known identity anchor available. A canonical LinkedIn URL is safer than a name alone, especially for common names.
Errors and limits
| Condition | Status and code |
|---|---|
| LinkedIn URL or supported identity is missing | 422 identity_required or 422 validation_failed |
Focused enrichment uses the organization and API-key per-minute buckets; it has no additional route cap. A field-level provider failure normally returns a successful response with that field set to null and a stable entry in meta.warnings. See Errors & rate limits.