API DOCUMENTATION / COUNTS AND RETURNED RECORDS
Counts and returned records
Separate result rows, distinct combined jobs, admitted requests, and returned-record usage units.
A count is a distinct included-job count
GET /v1/jobs/count returns {count, snapshot_watermark}. It counts distinct included combined job IDs using the same public-jobs filter builder as list queries; pagination, sorting, and representation options do not apply to count.
Compare counts with a matching snapshot
A count is computed at the returned projection watermark. Compare it with list results from the same query scope and watermark; pages collected across a publication change may not sum to the count. See the filter support table.
Returned-record usage counts response objects
For successful jobs list requests, returned records equal data.length; a successful job detail settles one record. Count settles zero. Company list/search settle the number of returned companies. Usage reports and placeholder routes settle zero. Monthly record usage is based on successful response settlement, not unique jobs over time.
A request and a record are different units
An authenticated request is admitted before route validation, so malformed requests can consume a request-window unit while returning zero billable records. A request rejected by an enforced rate window is recorded as uncharged. Each plan sets its monthly job and request allowance; see pricing.
Continue in the reference
Check related request behavior before you build.
View route status and methods Discuss API requirements