PDF Tamper Detector (HTPBE)

Checks PDF files for forensic evidence of post-creation modification — signature removal, incremental-update tampering, metadata date mismatches, editing-tool fingerprints, and more.

This actor is a thin wrapper around the HTPBE API. Bring your own API key — the actor performs no analysis itself, it calls your HTPBE account for you. Get a free key (test keys are unlimited, no card required) at htpbe.tech/api.

What it does

For each PDF URL you provide, the actor:

1. Submits it to POST /analyze
2. Retrieves the full result from GET /result/{id}
3. Pushes one dataset record per file with the verdict and full forensic detail

Each record includes:

• status — intact, modified, or inconclusive
• modification_markers — stable ids of the specific forensic signals that fired (e.g. HTPBE_SIGNATURE_REMOVED, HTPBE_DATES_DISAGREE); the full id → description dictionary is at htpbe.tech/how
• modification_confidence, usage_caution, and the rest of the result schema

Input

Field	Type	Required	Description
apiKey	string (secret)	Yes	Your HTPBE API key (htpbe_live_... or htpbe_test_...)
pdfUrls	array of string	Yes	Publicly accessible PDF URLs to check (max 10 MB each)

Try it for free without a key of your own

Use a free test key with the built-in mock URLs — no signup card, no quota consumed:

{
  "apiKey": "htpbe_test_YOUR_TEST_KEY",
  "pdfUrls": ["https://api.htpbe.tech/v1/test/modified-high.pdf"]
}

Get a test key instantly at htpbe.tech/api.

Notes

• 10 MB file-size limit per PDF; the source URL must be publicly downloadable without authentication.
• Structural/metadata analysis only — this does not detect visual or pixel-level content edits, and it is not a substitute for legal or forensic expert authentication.
• Every result carries a usage_caution field: a modification verdict describes the file, not the person who sent it, and must never be the sole basis for an automated adverse decision against someone.

Full API reference: htpbe.tech/api · Docs: github.com/htpbe/docs