Skip to main content
PATCH
Transition a claim's status
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

PATCH /publishing/claims//status Description: Moves a claim through the explicit state machine: filed → under_review | withdrawn, under_review → counter_claimed | resolved | escalated, counter_claimed → resolved | escalated, escalated → resolved. resolved and withdrawn are terminal. withdrawn may only be requested by the claimant themselves, and only from filed. Every other transition requires admin or owner. Records a system DisputeMessage and emits PUBLISHING_CLAIM_STATUS_CHANGED on success. Supports the Idempotency-Key header (route key p5.claim.transition) — a replay with the same key and body returns the cached response; the same key with a different body returns 409. Authorization:
  • RBAC: user or higher (finer-grained rules above are enforced in the service, not RBAC middleware)
  • Requires an active publisher addon
Method: PATCH

Code Examples

Authorizations

Authorization
string
header
required

JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"

Headers

Idempotency-Key
string

Path Parameters

id
string<uuid>
required

Body

application/json
toStatus
enum<string>
required
Available options:
filed,
under_review,
counter_claimed,
resolved,
escalated,
withdrawn
reason
string
required

Response

Claim updated

status
string
Example:

"success"

data
object

Ownership/share/metadata dispute filed against a work. Full claim lifecycle (transition, messages, evidence, bulk-resolve) is documented separately under publishing-claims.yaml; only the two work-scoped routes (file, list-for-work) live under /work.