cases

Cluster Confirm

P2 confirmation (PR-4b): the analyst accepts a cluster proposal — every member address is pinned with cluster metadata AND one cluster-confirmed event (carrying the FULL evidence object) is appended, atomically. The API boundary mirrors the pivot-not-member invariant: a poisoned request is a 422, never a silent fix-up.

post/v1/cases/{case_id}/cluster-confirm

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/cases/{case_id}/cluster-confirm
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Path parameters

case_idinteger required

Request body

pivotstring required
membersstring[] required
heuristicstring required
evidenceobject

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.