Skip to main content
Criteria define what makes a candidate a good fit. Nova stores them server-side and pulls them in automatically when scoring.

Criteria Lifecycle

Create criteria via AI generation from a job description, or manual creation one at a time.

Versioning

Calling Generate Criteria for a job that already has criteria replaces the existing set. Historical scores keep the criteria version they were scored against.
Criterion IDs are stable. Mutations create a new version, but each criterion keeps its original id.

Importance Levels

LevelImpact on ScoringExample
MUST_HAVEDisqualifier if unmet”Valid work authorization”
PREFERREDSignificant concern if missing”5+ years experience”
NICE_TO_HAVEMinor concern only”Open source contributions”

Answer Validation

CheckError Code
questionSetId required when answers providedVALIDATION_ERROR
Valid, existing question setQUESTION_SET_NOT_FOUND
Answer IDs match questions in the setANSWER_MISMATCH
Answer types match question typesANSWER_MISMATCH
If you include answers, answer every question in the set.

Available Operations

Generate Criteria

Create screening criteria from a job description

Get Criteria

Retrieve stored criteria for a job

Get Current Version

Retrieve active criteria with version metadata

List Versions

List historical criteria versions for a job

Get Version by ID

Retrieve a specific historical criteria version

Get Batch Criteria

Retrieve criteria for multiple jobs in one request

Set Criteria

Replace the entire criteria set for a job

Add Criterion

Add a single criterion to the job’s criteria

Edit Criterion

Update text or importance of a criterion

Remove Criterion

Remove a single criterion from the job

Archive Criteria

Archive criteria when a job closes

Criteria Library

Save common requirements once and reuse them across jobs.

Criteria Library

Store and reuse criteria across jobs

Next Step

Once you have criteria, you’re ready to Score Candidates.