Request Activity Claim

Payload for POST /{activity_id}/claim.

• message: optional note to the original poster
• organization_id: optional UUID. When set, the claim is made on behalf of that organisation. The claimant must be owner/admin in that org. On approval, the activity's organization_id is set, and edit rights flow through org membership (Claim v2).

Note: this project's claim_type column already exists with its own enum ('platform_organizer' | 'actual_owner' | 'general'). That field is unrelated to org-vs-individual and is left untouched by v2.

Imported-claim UX chapter (May 2026) — new optional fields:

• claim_method: which path the user picked in the relationship picker. Locked enum (owner_self | know_organizer | helping_claim | report_improve). Note 'report_improve' should NEVER reach this endpoint — that branch routes to the report endpoint instead. If it appears here we treat it as a malformed client request.
• claimant_relationship_label: free-text human context the user typed after picking a branch. e.g., 'I help with their marketing' or 'I'm their daughter'. Separate from claim_type's rigid taxonomy.
• imported_source_acknowledged: whether the user explicitly saw and acknowledged the imported-source badge before submitting. Audit signal for moderation.

Architectural note (locked decision): claim_method and claim_type are intentionally orthogonal. claim_type = the role I'm claiming AS (organiser, venue_owner, artist_representative, ...). claim_method = HOW I arrived at this claim (was I picking 'I'm the organizer' or 'I'm helping this get claimed'?). Keeping them separate is future-safe.