Add Criterion

Add a single criterion to a job’s screening criteria

POST /v1/jobs/{jobId}/criteria/items

@nova-sdk/api

TypeScript

import { Nova } from "@nova-sdk/api";

const nova = new Nova({
  apiKey: "sk_test_...",
  tenantId: "acme-corp",
});

const result = await nova.jobs.criteria.items.add({
  jobId: "job_abc123",
  body: {
    text: "Experience with GraphQL",
    importance: "NICE_TO_HAVE",
  },
});

201

{
  "criterion": {
    "id": "<string>",
    "text": "<string>",
    "order": 123,
    "createdAt": "2023-11-07T05:31:56Z"
  },
  "criteria": [
    {
      "id": "<string>",
      "text": "<string>",
      "order": 123,
      "createdAt": "2023-11-07T05:31:56Z"
    }
  ]
}

Existing scores aren’t affected. A new criteria version is created when you add a criterion. Only future score requests use the updated criteria.

No prior generation required. You can use this endpoint to create criteria manually without calling Generate Criteria first. If no criteria exist for the job, the first version (v1) is created automatically.

When to Use

Add a criterion when you want to build criteria manually or refine existing ones:

Manual Criteria

You already know your requirements and want to set criteria without AI generation

Discovered Requirement

Your team identified an important qualification that wasn’t in the original job description

Process Change

Your hiring process evolved and now requires evaluating an additional skill

From Library

Copy a reusable criterion from your Criteria Library

Common Scenarios

Scenario	Example Criterion
Team feedback after interviews	”Experience mentoring junior engineers”
New project requirements	”Familiarity with GraphQL APIs”
Compliance update	”Security clearance eligibility”
From library	Copy a reusable criterion from your Criteria Library

Adding from Library

To add a criterion from the library to a job, first list your library criteria, then add the selected criterion to the job:

// 1. Get library criteria
const { criteria: libraryCriteria } = await fetch(
  `https://embed.nova.dweet.com/v1/criteria-library`,
  { headers: { 'Authorization': `Bearer ${apiKey}`, 'X-Tenant-Id': tenantId } }
).then(r => r.json());

// 2. User selects a criterion from the library UI
const selected = libraryCriteria[0];

// 3. Add it to the job (creates a copy)
await fetch(`https://embed.nova.dweet.com/v1/jobs/${jobId}/criteria/items`, {
  method: 'POST',
  headers: {
    'Authorization': `Bearer ${apiKey}`,
    'X-Tenant-Id': tenantId,
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    text: selected.text,
    importance: selected.importance,
  }),
});

Adding from the library creates an independent copy. Editing the job criterion won’t affect the library, and vice versa.

Response

The response includes the full criteria list after the addition, making it easy to update your UI without a separate GET request.

Authorizations

Authorization · string · header · required

Use Authorization: Bearer sk_test_* or Authorization: Bearer sk_live_*.

Headers

X-Tenant-Id · string · required

Your customer identifier. Tenants are auto-provisioned on first request.

Idempotency-Key · string

Optional key that makes criteria and library mutation requests safe to retry without duplicating side effects. The namespace is shared across all API keys for the same partner and environment. Reuse the same key when retrying the same request parameters.

Required string length: 1 - 255

Path Parameters

jobId · string · required

Your job identifier (external ID).

Body

application/json

text · string · required

Minimum string length: 1

importance · enum<string> · required

Available options: MUST_HAVE, PREFERRED, NICE_TO_HAVE

Response

201

application/json

Created

criterion · object · required

Show child attributes

criteria · object[] · required

Show child attributes