Skip to main content
PATCH
/
v1
/
jobs
/
{jobId}
/
criteria
/
items
/
{criterionId}
Edit criterion in active criteria
curl --request PATCH \
  --url https://embed.nova.dweet.com/v1/jobs/{jobId}/criteria/items/{criterionId} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --header 'X-Tenant-Id: <x-tenant-id>' \
  --data '
{
  "text": "<string>",
  "importance": "MUST_HAVE"
}
'
{
  "criterion": {
    "id": "<string>",
    "text": "<string>",
    "importance": "MUST_HAVE",
    "order": 123
  },
  "criteria": [
    {
      "id": "<string>",
      "text": "<string>",
      "importance": "MUST_HAVE",
      "order": 123
    }
  ]
}
Existing scores are not affected. A new criteria version is created when you edit a criterion. Only future score requests will use the updated criteria.

​
When to Use

Edit a criterion when you need to refine an existing requirement:

Adjust Importance

Change a criterion from NICE_TO_HAVE to MUST_HAVE (or vice versa) based on candidate pool quality

Clarify Wording

Make the criterion more specific or easier to evaluate

​
Partial Updates

You can update just the text, just the importance, or both. At least one field must be provided. 
{
  "importance": "MUST_HAVE"
}

​
Response

The response includes the full criteria list after the edit, 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.

Path Parameters

​
jobId
string
required

Your job identifier (external ID).

​
criterionId
string
required

Criterion ID.

Body

application/json
​
text
string
​
importance
enum<string>
Available options:
MUST_HAVE,
PREFERRED,
NICE_TO_HAVE

Response

Updated

​
criterion
object
required
​
criteria
object[]
required