Skip to main content
Scoring submissions are idempotent by default. This makes it safe to retry requests without creating duplicate scoring jobs.

​
How idempotency works

For POST /v1/jobs/{jobId}/applications/{applicationId}/scoring-jobs, Nova deduplicates requests using:
  • Your tenant (from X-Tenant-Id and your API key)
  • jobId
  • applicationId
If you submit the same jobId and applicationId again, Nova returns the existing scoring job.

​
Re-scoring

To create a new scoring job for an application, set rescore: true.
Re-scoring is idempotent per criteria version. If you submit rescore: true multiple times without changing criteria, you will get the same re-score job.

​
Pinning a criteria version

If you want to score against a specific criteria version, include criteriaVersionId: 
{
  "resumeUrl": "https://storage.example.com/resumes/abc123.pdf",
  "rescore": true,
  "criteriaVersionId": "criteria_version_id"
}

​
What creates a new scoring job

ChangeNew job created
jobId changesYes
applicationId changesYes
rescore changes from false to trueYes
criteriaVersionId changes while rescore: trueYes
resumeUrl changesNo
candidateData changesNo
  1. Retry network failures.
  2. Retry 5xx errors with exponential backoff.
  3. For 429, wait for Retry-After before retrying.
If a scoring request fails because the resume URL is inaccessible, generate a new URL and retry the request. Since the job was not created, the retry is safe.