---
title: "Attach Signed Artifact"
method: POST
path: "/v1/cases/{case_id}/exhibits/from-report"
tags: ["cases"]
---

# Attach Signed Artifact

`POST /v1/cases/{case_id}/exhibits/from-report`

## 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}/exhibits/from-report`
- Auth: one of:
  - API key in header `X-API-Key`
  - HTTP bearer

Attach an ISSUED signed artifact to the case by content hash — the only
intake for signed children (B6). The server resolves the hash against its
own registries (compliance_reports, then signed_artifacts); caller bytes
are never accepted. The attach is an analyst act → case.exhibit.attached
in the same breath, and bundle assembly re-resolves at seal time.

## Path parameters

- `case_id` integer, required

## Request body

- AttachArtifact
  - `content_hash` string, required

## 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)