> ## Documentation Index
> Fetch the complete documentation index at: https://docs.samsa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Download a result PDF

> Fetch a digitally signed PDF record of a past detection result, available for 24 hours.

```
GET https://detect.samsa.ai/v1/public/detect/result/{request_id}
```

Returns a digitally signed PDF record of a past detection result. Use it when you need
a shareable, verifiable artifact of a check — a compliance record, an attachment to a
report, or evidence in a review.

The PDF is available for **24 hours** after the original check. It contains no PII: no
IP address, no user agent, no filename, and none of the uploaded bytes — only the
verdict facts, the `request_id`, a coarse region bucket, and the timestamp.

## Request

`request_id` is the UUID returned by
[`POST /v1/public/detect`](/content-verification/detect). The endpoint takes no
parameters and no authentication.

```bash curl theme={null}
curl -o result.pdf \
  https://detect.samsa.ai/v1/public/detect/result/c1a2b3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d
```

<Note>
  The detect response also carries a ready-made `result_pdf_url`. **Follow that URL
  exactly as returned** rather than assembling one yourself — it and the path above
  serve the identical signed PDF. `result_pdf_url` is `null` when result persistence is
  unavailable; in that case there is no PDF to fetch.
</Note>

## Response

`200 OK` with `Content-Type: application/pdf` and the following headers:

| Header                   | Value                                                     |
| ------------------------ | --------------------------------------------------------- |
| `Content-Disposition`    | `attachment; filename="samsa-detection-<request_id>.pdf"` |
| `Cache-Control`          | `private, max-age=<seconds left in the 24h window>`       |
| `X-Content-Type-Options` | `nosniff`                                                 |

The document restates the verdict, the per-technique outcome, the record metadata
(`request_id`, response timestamp, coarse region bucket), and the independent
verification link.

## Signature

The PDF carries a PAdES-style detached PKCS#7/CMS signature, applied as a PDF
incremental update — so the file re-parses as an ordinary PDF and any standard PDF
reader can open it. It is signed with the same signer identity Samsa's C2PA signing
path uses, so authenticity is verifiable against the same certificate chain. A
tampered byte or a wrong CA root fails verification.

If the signer is not configured, the endpoint returns `503` rather than an unsigned
PDF — an unsigned result is never served.

## Errors

Errors return `{"detail": "…"}` — not the Samsa REST API
[error envelope](/guides/errors).

| Status | When                                                                                                                                              |
| ------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `404`  | The `request_id` is unknown or is not a UUID.                                                                                                     |
| `410`  | The result is older than the 24-hour availability window. The record may persist for retention purposes, but the PDF is issued for 24 hours only. |
| `503`  | The detection store or the result signer is temporarily unavailable. The response carries a `Retry-After` header — retry.                         |

<Tip>
  Fetch the PDF while it is fresh and archive it on your side if you need it beyond
  24 hours. Once the window closes the endpoint returns `410` and the document cannot
  be reissued.
</Tip>