Skip to main content
POST
Register an uploaded evidence file on a claim
This endpoint requires authentication. Include your Bearer token in the Authorization header.

Description

POST /publishing/claims//evidence/attach Description: Companion to POST /publishing/claims/{id}/evidence — after the client’s signed PUT to GCS succeeds, call this to append the file to the claim’s evidenceUrls array and record a system message. fileKey must fall under the tenant+claim-scoped prefix returned by the evidence endpoint. Idempotent on fileKey — repeat calls with the same key return the claim unchanged, no duplicate row. Supports the Idempotency-Key header (route key p5.claim.evidence-attach). Authorization:
  • RBAC: user or higher; claimant-or-admin check enforced in the service
  • Requires an active publisher addon
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

id
string<uuid>
required

Body

application/json
fileKey
string
required

Must start with claims-evidence/{tenantId}/{claimId}/ — the prefix returned by the evidence endpoint.

fileName
string
required
mimeType
string
required
size
integer
required

Bytes. Must not exceed 25 MB (26214400).

Response

Evidence attached (or already-attached claim returned unchanged)

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.