Pagination & filtering

Pagination

Collection endpoints accept:

Parameter	Description
`page`	One-based page number. Default: `1`.
`pageSize`	Records per page. Default: `10`; maximum: `100`.

Paginated responses use the canonical
{ data, meta: { pagination } } envelope. Use the pagination metadata rather
than inferring the last page from its item count.

Candidate filters

GET /candidates supports:

Parameter	Description
`job_id`	Restrict results to a job in the credential's CVViZ account.
`status`	Restrict results to a workflow status. Requires `job_id`.
`updated_since`	Return profiles updated at or after an RFC 3339 timestamp. A timezone is required.

Candidate stages and applications

GET /jobs/{jobId}/candidate-stages returns the configured hiring pipeline for
a job. Use the stage code to interpret per-job candidate status values. A
negative stage code represents a rejection stage.

GET /candidates/{candidateId}/applications returns the jobs associated with a
candidate and the candidate's current stage in each job. appliedAt is the
earliest known association with the job; updatedAt is the most recent known
application update.

Example: candidates updated for a job

Replace 901 with your job ID. Add only filters documented by that endpoint;
do not assume a filter supported by candidates is also supported by jobs.

Dates and units

Use RFC 3339 timestamps with a timezone, for example 2026-09-01T00:00:00Z.
Job experience bounds are in years; candidate experienceMonths is in
months. Read field descriptions before comparing values across resources.

Synchronization limits

Page-based results can change while you read them. Deduplicate by resource ID.
Candidate updated_since filters profile updates; it is not a complete event
feed for every related note, application or deletion. Do not assume snapshot
pagination or deletion notifications that the reference does not promise.

Pagination#

Candidate filters#

Candidate stages and applications#

Example: candidates updated for a job#