Skip to main content
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. The endpoint takes no parameters and no authentication.
curl
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.

​
Response

200 OK with Content-Type: application/pdf and the following headers: 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.
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.