Overview
The Enrich endpoint combines resolution and data enrichment in a single call. It first resolves the person identity using fuzzy matching, then returns comprehensive profile data including demographics, work history, education, addresses, and contact information. Note: Consider upgrading to/v2/enrich for direct PID/LinkedIn lookups, selective field returns, and improved performance.
Request
Headers
Your API key for authentication
application/json
Request Body
An array of person records to enrich. Maximum 500 records per request.
Request Example
Response
Response Structure
Unique identifier for this API request
Array of enrichment results
ISO 8601 timestamp when the request was completed
Result Object - Demographics
Your identifier from the request
Whether a match was found
Minerva person identifier
Person’s full name
First name
Middle name
Last name
Name suffix
Gender (“M” for male, “F” for female, or null)
Date of birth (ISO 8601 format)
Current age
Marital status (“M” for married, “S” for single, or null)
Household identifier
Spouse’s Minerva PID if available
Number of children
Result Object - Financial
Whether the person is retired
Estimated income bracket
Estimated wealth bracket
Home ownership status (e.g., “Owner”, “Renter”, or null)
Result Object - Social & Professional
LinkedIn profile URL
Current title from LinkedIn
Industry from LinkedIn
Whether the person likely works remotely
Facebook profile URL
Twitter profile URL
Result Object - Legal Records
Whether bankruptcy records exist
Whether judgment records exist
Result Object - Contact Information
Array of personal email addresses with ranking
Array of professional email addresses with ranking
Array of phone numbers with type and ranking
Result Object - Address History
Array of address records with property details
Result Object - Work Experience
Array of work history records
Result Object - Education
Array of education records
Result Object - Other Fields
Confidence score for the match (0-1 scale)
Any validation errors from the input
Error Responses
400- Bad Request: Missing required fields or malformed JSON401- Unauthorized: Invalid or missing API key413- Payload Too Large: More than 500 records in request422- Unprocessable Entity: Validation errors in record data (invalid field names, data types, or values)500- Internal Server Error: Unexpected server error
Notes
- Maximum 500 records per request (lower than
/resolvedue to data volume) - All list fields (emails, phones, addresses, work, education) return empty arrays
[]if no data is available - Dates are returned in ISO 8601 format (YYYY-MM-DD)
- Financial figures are in USD
- Arrays are ordered by rank, with rank=1 being the most recent/relevant

