For the complete documentation index, see llms.txt. This page is also available as Markdown.

Schedule Run History

What each recent run found - jobs, contacts and usable emails.

POST /jobs_schedule_runs

The recent runs of one schedule, newest first: how many jobs each found and how many were new, how many people it added to the list, and how many of them have a usable email.

Free. credits_used is always 0.

Headers

Name
Value

Content-Type

application/json

Body

Name
Type
Description

api_key

string

Required. Your API key.

schedule_id

integer

Required. From List Schedules.

limit

integer

How many recent runs. Default 10, most 50.

Response

data.runs is a list, newest first. Each run has:

Field
Description

run_id

The run's id.

trigger

What started it: scheduled, run_now, created (a schedule saved with run_now) or manual (a one-off search into the same list).

status

The jobs part: processing, done, not_found (no jobs) or error. A scheduled run skipped for too few credits is error, with the reason in error.

started_at, finished_at

When the jobs part started and finished.

jobs_found

Jobs the search returned.

jobs_new

Jobs saved because they were not already on the list. These are the ones charged.

job_credits_used

Credits for the jobs: 0.1 x jobs_new.

contact_search_status

The people search: not_requested, queued, processing, done or error.

contacts_found

People added to the list by this run.

usable_emails

Of those, people with a valid or accept-all email. Same rule as the Lists page's Verified Email Count.

counts_final

false while this is the newest run.

error

Why a run failed or was skipped, or null.

Example