Search Contact Finder
Search Contact
Search Contact Finder
Re-fetch a previous Search Contact job by job_id.
GET
Search Contact Finder
Search Contact returns results synchronously from the launcher. Use this endpoint to re-fetch or audit a previous job — not to poll for completion.
When to use this
Pass thejob_id returned by Search Contact Launcher to retrieve the same job state, original input echo, and output.persons without re-running the search.
What you get
The response mirrors the launcher response exactly:| Field | Description |
|---|---|
input.task | Echo of all request fields plus job_id and context_id |
output.persons | Array of contacts found — same shape as the launcher response |
professional_email, mobile_phone, etc.) are always null in Search Contact output. Use Contact Enrichment to retrieve them.Authorizations
To access the API, provide your API key in x-api-key.
Query Parameters
The unique job_id you want to query. This value is returned by the corresponding launcher endpoint.
A UUID.
Example:
"7d44db58-5de3-4e92-a2fb-8325d12c2e8b"
Response
Search Contact job state, input, and any available output.
Search Contact response with job state, input, and optional output.
The status of the job.
Available options:
RUNNING, SUCCEEDED, FAILED, TIMED_OUT, ABORTED Example:
"RUNNING"
A date time in ISO 8601 format.
Example:
"2025-02-05T15:46:35.771751+00:00"
Example:
{
"task": {
"domain": "waterfall.io",
"page_number": 1,
"page_size": 10,
"job_id": "7d44db58-5de3-4e92-a2fb-8325d12c2e8b",
"context_id": "7d44db58-5de3-4e92-a2fb-8325d12c2e8b"
}
}A date time in ISO 8601 format.
Example:
"2025-02-05T15:46:35.771751+00:00"
Search Contact output payload.
Example:
{ "persons": [] }