Integration manual
Verifiable documents
Issue a PDF with per-page proof links and give recipients a place to check it.
Issue the document
Activate a documents allowance. Production issuance requires an approved issuer identity. Submit an unencrypted PDF of 1–5 pages, up to 10 MB. A footer is added outside the original page content, with a proof QR for each page. Save the returned document id and download the issued PDF.
curl https://eu.mimeprotect.com/api/security/documents \
-H "Authorization: Bearer $MIMEPROTECT_API_KEY" \
-F "document=@statement.pdf"Share the issued copy
Distribute the returned PDF, rather than your unstamped source. Its signed record binds the exact file digest to the issuing account, environment, key and retention period. Sandbox files are prominently marked as tests. Default retention is 30 days; export your evidence and arrange extended retention where required.
Check a copy
Recipients can use Verify a document on the homepage or /verify. Server integrations submit a file to the verification endpoint. Inspect status and scope: HTTP 200 only means the check returned a result.
curl https://eu.mimeprotect.com/api/security/verify-document \
-H "Authorization: Bearer $MIMEPROTECT_API_KEY" \
-F "document=@issued-statement.pdf"Interpret the evidence
An exact match establishes the issued digital file’s integrity. A different file can be an edit, scan or conversion; it is not automatically fraud. A photo, unclear scan or unsupported proof must not be treated as a match. Print/scan OCR comparison requires a separately validated content-comparison engine and a proof with content manifests; exact-file proofs do not provide that scope.
Ready to connect it?
Open your regional workspace, create a sandbox key and test the complete flow with synthetic data. Keep the returned identifiers and inspect every result before moving to production.
Open the sandbox →Discuss your requirements →