---
title: "Registry Dispute"
method: POST
path: "/v1/registry/dispute/{content_hash}"
tags: ["registry"]
---

# Registry Dispute

`POST /v1/registry/dispute/{content_hash}`

## Request

- Base URL: `https://api.bitpoort.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.bitpoort.com/v1/registry/dispute/{content_hash}`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Right of reply (road 5.4): file a signed dispute on one PUBLIC row. Keyed (a keyed exception
under the public prefix): a dispute is never anonymous, and the key id rides the signed body so
the desk can answer. Idempotent on content: the same dispute twice is one artifact.

## Path parameters

- `content_hash` string, required

## Request body

- DisputeIn: What the disputing party sends. The claim is their own words (stored, signed, never shown on the public surface); the contact is never stored -- only its digest rides the signed body.
  - `claim` string, required
  - `evidence_urls` string[]
  - `contact` string, nullable

## Response `200`

Successful Response

- object

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/bitpoort/apis/bitpoort-api.md) · [All operations](https://skmtc.dev/bitpoort/apis/bitpoort-api/llms.txt) · [OpenAPI document](https://skmtc.dev/bitpoort/apis/bitpoort-api/revisions/1a51d8566777?raw)