Skip to main content
GET
Availability: Agency plan, on https://app.gethuntd.com. Other plans receive 403 ENDPOINT_NOT_ON_PLAN. Polling is free but counts toward your API key’s rate limit.

Overview

Retrieve the progress of an email check and, once it’s finished, the answer for each source. Returns 200 for any job that exists: read status to know whether it’s done.

Reading the Result

For each source, is_user is the answer:
Only read is_user once the job’s status is completed. Until then it’s null for every source, even ones that have already finished. All answers are released together.
checked_at is when the check actually ran, so a cached answer (cached: true) keeps its original date and can be older than the job.

Job Status

Polling Strategy

  1. Wait until the poll_after time from the submit response (skip this if it was null)
  2. Poll every 5 seconds, backing off toward 60 seconds
  3. Stop when status is completed
A job queued for hours usually isn’t stuck: checks only run Monday to Friday, 09:00 to 18:00 in your account’s timezone. There is no webhook for this endpoint, so for long waits save job_id and check back from a scheduled job.

Errors

Authorizations

X-API-Key
string
header
required

API key in format: hntd_{id}_{secret}. Create one in Settings → API & webhooks. Authorization: Bearer is also accepted.

Path Parameters

job_id
string<uuid>
required

The job ID returned by Submit Email Check

Example:

"8f4c2a90-6c1e-4b58-9a2f-1d3e5b7c9011"

Response

The job's progress, and its answers once completed

success
enum<boolean>
Available options:
true
job_id
string<uuid>
Example:

"8f4c2a90-6c1e-4b58-9a2f-1d3e5b7c9011"

email
string
Example:

"dana@acme.com"

status
enum<string>

completed means every source is done or failed, and the answers are filled in.

Available options:
queued,
running,
completed
sources
object

One entry per source slug.