Skip to main content
GET
Prospector Finder
Use the job_id returned by Prospector Launcher to fetch state and results.

Polling vs webhook

If you passed webhook_url when launching the job, you don’t need to call this endpoint at all — Waterfall will automatically POST the result to your URL as soon as the job is ready. If you didn’t use a webhook, poll this endpoint until status is SUCCEEDED:
Use short exponential backoff — start with a 5s delay, then 10s, then 20s.

Job states

What you get

The output object contains two keys: The number of persons returned is controlled by the limit parameter set at launch (default 10, max 500).

Authorizations

x-api-key
string
header
required

To access the API, provide your API key in x-api-key.

Query Parameters

job_id
string<uuid>
required

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

Prospector job state, input, and any available output data.

Finder response with prospector job status, input, and optional output.

status
enum<string>
required

The status of the job.

Available options:
RUNNING,
SUCCEEDED,
FAILED,
TIMED_OUT,
ABORTED
Example:

"RUNNING"

start_date
string<date-time>
required

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

input
object
required
stop_date
string<date-time>

A date time in ISO 8601 format.

Example:

"2025-02-05T15:46:35.771751+00:00"

output
object