Skip to main content
POST
File an ownership/share claim on a work
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

POST /work/works//claims Description: Files a WriterClaim (Phase 5). Caller must be an admin/owner OR the writer identified by claimantWriterId must actually be linked to the work (403 otherwise). New claims start in filed status. Supports an Idempotency-Key header (routeKey p5.claim.file) — a replayed key with an IDENTICAL body returns the original response; the same key with a DIFFERENT body returns 409. This endpoint only covers work-scoped filing/listing; the full claim lifecycle (transition, messages, evidence, bulk-resolve) lives under /publishing/claims (see publishing-claims.yaml). Authorization:
  • Required role: user or higher
Method: POST

Code Examples

Authorizations

Authorization
string
header
required

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

Headers

Idempotency-Key
string

Path Parameters

workId
string<uuid>
required

Body

application/json

Caller must be an admin/owner on the tenant OR the writer named by claimantWriterId must actually be linked to the work — otherwise a 403. New claims always start in filed status.

claimantWriterId
string<uuid>
required
claimedRole
enum<string>
required
Available options:
CA,
C,
A,
AR,
SA,
SR,
TR,
PA
claimType
enum<string>
required
Available options:
ownership,
share_dispute,
registration_conflict,
metadata
claimedShares
object
parentClaimId
string<uuid> | null
evidenceUrls
string[]

Response

Claim filed

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.