Skip to main content
DELETE
/
v1
/
jobs
/
{jobId}
/
criteria
/
items
/
{criterionId}
Remove criterion from active criteria
curl --request DELETE \
  --url https://embed.nova.dweet.com/v1/jobs/{jobId}/criteria/items/{criterionId} \
  --header 'Authorization: Bearer <token>' \
  --header 'X-Tenant-Id: <x-tenant-id>'
{
  "success": true
}
Existing scores are not affected. A new criteria version is created when you remove a criterion. Only future score requests will use the updated criteria.

​
When to Use

Remove a criterion when it’s no longer relevant to the role:

Requirement Changed

A skill or qualification is no longer needed for the position

Too Restrictive

The criterion is filtering out otherwise qualified candidates

​
Common Scenarios

ScenarioAction
Technology pivotRemove criteria for deprecated tech stack
Budget changeRemove seniority requirements if hiring at different level
Team restructureRemove criteria for responsibilities that moved to another role
Consider the impact on scoring consistency. Removing a MUST_HAVE criterion may significantly change how candidates are evaluated compared to earlier applicants.

​
Response

Returns a success flag: 
{ "success": true }
To refresh your UI, call Get Criteria.

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.

Response

Removed

​
success
boolean
required