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
| Level | Impact on Scoring | Example |
|---|---|---|
MUST_HAVE | Disqualifier if unmet | ”Valid work authorization” |
PREFERRED | Significant concern if missing | ”5+ years experience” |
NICE_TO_HAVE | Minor concern only | ”Open source contributions” |
Answer Validation
| Check | Error Code |
|---|---|
questionSetId required when answers provided | VALIDATION_ERROR |
| Valid, existing question set | QUESTION_SET_NOT_FOUND |
| Answer IDs match questions in the set | ANSWER_MISMATCH |
| Answer types match question types | ANSWER_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