Count jobs

How many jobs match your filters, without returning them. Use it to size a plan or to estimate a backfill before you start.

GET/v1/active-ats-count

Parameters

ParameterTypeDescription
time_framestring1m (default) counts every job first collected in the last 31 days, including jobs that have since expired: the volume you would have received by polling for a month. 1h, 24h, 7d and 6m count active jobs and match what /v1/active-ats returns for the same window.
titlestringSearch the title. nurse manager needs both words, "nurse manager" is a phrase, nurse OR manager either, -assistant excludes, engineer* is a prefix.
descriptionstringSame syntax, over the title, employer name and description together.
locationstringFull place names, City, Region, Country, combined with OR. See Location search.
title_advanced, description_advanced, location_advanced, organization_advancedstringBoolean expressions with &, |, !, <->, parentheses and :*. They take precedence over the plain parameter. See Advanced search.
date_posted_gte, date_posted_ltISO 8601When the employer says the job was posted. A time without a zone is UTC.
date_created_gte, date_created_ltISO 8601When we first collected the job. Use these to replay a missed window exactly. See Time fields.
countrylistCA, US or both (the default).
organization, exclude_organizationlistExact, case-sensitive employer names, comma-separated. Quote a name that contains a comma: "Acme, Inc.". The organization list has every name.
source, exclude_sourcelistSource systems, e.g. workday,icims. See Sources.
has_salarybooleantrue: the employer published pay. false: it did not.
remotebooleantrue: marked remote by the employer. false: not remote.
has_no_locationbooleantrue: jobs without a resolved location.

Example

bash
curl --get "https://api.thejobsapi.com/v1/active-ats-count" \
  -H "Authorization: Bearer $THEJOBSAPI_KEY" \
  --data-urlencode 'time_frame=1m' \
  --data-urlencode 'location=British Columbia, Canada' \
  --data-urlencode 'title=nurse'
json
{ "count": 3821 }

Counts scan every matching job, so broad 6m searches with many terms can take several seconds. A count counts as one request and no jobs.