Person Search
Contact Job Results
Unlock a completed contact job (billing once) and retrieve a page of matched contacts; GET pages afterward without re-billing
POST
Overview
Contact job results are locked until you unlock them.
If you call
GET before unlocking, the API returns 409 Conflict telling you to POST first.
Billing
Unlock bills net-new Minerva PIDs for your organization in the current billing year (previously unlocked PIDs are not re-charged). Usage is published as theplatform_records_under_management metric.
- Insufficient credits → unlock fails; retry after adding credits
- Successful unlock is idempotent: later
POST/GETcalls do not re-bill billable_countin the response is the number of PIDs charged for this job
Request
Headers
string
required
Your API key for authentication.
Path Parameters
string
required
UUID of a completed contact job owned by your organization.
Query Parameters
integer
Page size. Defaults to
100. Range: 1–100.integer
Number of results to skip. Defaults to
0.Response
Success Response (200 OK)
Same shape for POST (unlock) and GET (page).
string
Job UUID.
string
contact_append or contact_prospect.object[]
Page of matched contacts.
string
Minerva person ID (
p-…).string
The requested job title this contact matched.
string
Current job title on file, when available.
object
Input company that matched (contact-append only). May include
name, domain, and/or linkedin_url.string
Input NAICS code that matched (contact-prospect only).
object
Enrichment payload for the person (lowercased column names from the enrichment dataset).
integer
Total stored results for the job (
result_count).integer
Number of results in this page.
integer
Echo of the requested
limit.integer
Echo of the requested
offset.integer
Net-new PIDs charged when the job was unlocked.
string
ISO-8601 timestamp of the successful unlock.
Response Example