Endpoint
POST /contacts/researchCredits
By default 1 for email, 5 for phone,
6 for both, per contact.
Details
Inputs
Send either search results or identities. You do not need to search first.
Optional fields:
listIds: add each researched contact to one or more Seamless lists.researchTypes: research["email"],["phone"], or both for every contact. Omit it to use your Contact Data settings. See Contact research costs.skipDeduplicationCheck: re-research a contact your org researched recently. This uses credits again.isJobChange: run a job change check instead. See the Job Change API.
What you get back
The Data dictionary lists every field.
Example
requestId per contact. Poll until status is done:
Response (trimmed)
Common poll statuses:
queued, researching, done, duplicate, not found, missing, and error. A duplicate status means your org already
researched this contact. Read it from the My Contact Data
API instead of paying to research it again.
not found means no match for the identifiers; missing means the server
has no record of that requestId.POST /contacts/research/single takes one searchResultId (or one contact object, optionally with isJobChange) and returns one requestId to poll the same way.
For Python, JavaScript, and other languages, see Research contacts in the API reference.