Skip to main content
PUT
Set a change's manual priority
This operation starts with internal qualification and must be enabled for your organization. Triage eligibility, an active review seat and current repository access are required.
A priority change records the authenticated actor in Triage history and preserves its notifications. You can change a manual priority, but you cannot clear it to restore calculated ranking.

Read before writing

Read GET /v1/triage/changes/{id} and use data.priority.revision as expected_revision. This opaque value is a concurrency precondition, not a credential or the displayed score. A null or absent revision means the precondition is unavailable; reread instead of constructing one. List responses do not supply this detail-only field.
Stop if the first jq command fails. Use the change’s returned UUID, not its provider PR number. Generate this file once per new decision; for retries, reuse it without rerunning these commands.

Retry an uncertain result

Retry the exact same body with the original expected_revision and idempotency_key. Duplicate detection precedes stale-state checks. A duplicate response returns the latest current state, which may reflect another user’s later decision; it does not reapply your change. That current state can include close_candidate, although this endpoint cannot set it. A new command with a stale precondition conflicts with the current state. Reread before making a new decision, using a new command key. Obtain revisions from the selected change and organization; a valid revision never bypasses permission checks. Hosted MCP exposes set_triage_change_priority with account:read, triage:read and triage:write consent. For workspace keys, send the organization selector org_id in the query on the detail read and in the JSON body on this update. Organization-scoped keys omit it.

Authorizations

x-coderabbitai-api-key
string
header
required

API key for authentication. You can create an API key from the CodeRabbit dashboard.

Path Parameters

id
string<uuid>
required

Body

application/json
urgency
enum<string>
required
Available options:
p0,
p1,
p2,
p3
expected_revision
string
required

Use priority.revision from the current change detail. Retain this value and idempotency_key when retrying the same command.

Required string length: 1 - 2048
idempotency_key
string
required

Unique command identity. A repeated key returns the native current state without applying another change.

Required string length: 1 - 255
org_id
string
reason
Maximum string length: 200

Response

OK

status
enum<string>
required
Available options:
updated,
duplicate
current
object
required