Forensic PDF API
HTPBE? is a forensic PDF API. It examines the file itself – not the text printed on the page – and reports whether the PDF was changed after it was created. You submit a document URL, then read back a verdict (intact, modified or inconclusive) with a confidence level and named markers for every finding. This page covers what the forensic layer looks at, what the result contains and how to route it. For the integration pitch, see the API page; self-serve keys and free test keys are available on every plan.
The problem
Modern document fraud is invisible to visual review
A growing class of document fraud opens a genuine PDF, edits a balance, a date, or a beneficiary, and re-saves it. Visually nothing changes – the document passes pixel-level review, layout review, and KYC.
Structural PDF analysis reads the layers rendering engines never expose: revision history, object structure, signature coverage maps. That is where edits leave fingerprints they cannot wipe.
Common tampering patterns
- Modified balances or totals after export
- Swapped IBAN or beneficiary on invoices
- Post-signature edits on contracts
- Backdated issue and modification dates
- Fabricated documents from consumer PDF tools
What this looks like
What the forensic PDF API analyzes
Three real fraud mechanics we catch at the structural PDF layer.
Edit history
Edits saved into a PDF after it was created leave structural evidence. The forensic PDF API detects it and reports that the file was re-saved after the issuer generated it.
Origin and editing-tool forensics
The API maintains a database of hundreds of PDF tool fingerprints – institutional generators, consumer editors and online editing services. When a document carries the fingerprints of a known PDF editing tool, or its structure contradicts its stated origin, the API returns a high-confidence named marker.
Digital signatures
The API reports whether a document was signed, whether anything changed after signing, and whether a signature was removed. Post-signature changes and signature removal are returned at the highest confidence level because they are the clearest tamper evidence a file can carry.
Document assembly
Some forgeries are built by combining pages from several sources. The API flags documents whose pages come from independent renderings or inconsistent tooling, which a reader cannot see on screen.
Page content and images
Values replaced on a page, text laid over a scan, covered-over regions and edited embedded images are reported as named findings.
Dates and metadata consistency
Creation, modification and metadata timestamps are cross-checked against each other. Contradictory, impossible or out-of-sequence dates come back as markers that say what disagrees, not just that something does.
How the forensic PDF API fits
Scope
What a forensic verdict covers – and what it does not
Know which question this layer answers before you wire it into a decision.
The forensic PDF API answers one question: was this file changed after it was created? It does not read the figures in the document or confirm that the content is true. A document built from scratch and exported once has no edit history to find, and files from consumer software, online editors, scans and filled forms come back as inconclusive rather than clean, with the reason spelled out. Use the result alongside content checks and issuer confirmation, not instead of them.
What HTPBE? checks
Detection capabilities
Deterministic structural signals. No probabilistic scores, no model training.
Stated origin contradicted
The file’s structure contradicts the origin it states – a common sign of editing after export.
Post-creation edits
Detects documents that were changed and saved again after they were first produced, and reports them with a named marker.
Pages from multiple sources
Documents assembled from pages of different files – a page swapped in from another statement, a forged page spliced into a genuine pack.
Date inconsistencies
Creation and modification dates that contradict each other, or dates that could not be real. Either is a sign the file changed after it was issued.
Digital signature validation
When a document is digitally signed, HTPBE? checks whether it changed after signing or had its signature removed. Either finding returns a certain-confidence verdict.
Replaced or overlaid text
Detects text replaced or added on a page after the document was produced – without relying on how the page looks on screen.
Share with engineering
Wire this into your intake pipeline in under a day
Two API calls – one POST to submit the PDF, one GET to retrieve the verdict. Forward this page to your engineering team; the full API reference, quotas, and copy-paste examples in cURL, JavaScript, Python, PHP, Go, and Ruby are one click away.
Pricing
Self-serve plans, no sales call
All plans include the same forensic checks. Pick the quota that matches your monthly document volume.
manualStarter
30 credits/mo
Manual spot-checks and integration testing
most commonGrowth
350 credits/mo
Active document processing pipelines
high volumePro
1,500 credits/mo
High-volume automation and API integrations
Enterprise (unlimited, on-premise available) — see full pricing
API key on signup. Free test environment on every plan. No card required.
Customer stories
Teams that stopped document fraud
Compliance, finance, and risk teams use HTPBE? to catch manipulated PDFs before they become costly mistakes.
Caught an invoice where the total had been changed by less than a thousand dollars. Without this I would have approved it without a second look.
Sarah M.
AP Manager
United States
We had three applicants in the same week with bank statements that looked completely fine. Two of them were flagged as modified. You simply cannot see this by reading the document – it is in the file structure.
Lars V.
Risk Analyst, Online Lending
Netherlands
Salary slips were coming with altered figures. We identified two problematic files before the placement was finalised.
Priya K.
HR Operations Lead
India
Since we started checking documents this way, we stopped two applications early in the process that would have been very difficult to reverse later.
Julien R.
Fraud Analyst, Fintech
France
Some applicants were sending PDFs that looked authentic but had been edited in ways not visible to the eye. We now ask for checked originals when something is flagged. Already saved us from a few bad decisions.
Marta S.
Compliance Coordinator
Spain
One invoice was caught because there was a mismatch between the document dates and structure. That particular case would have cost us significantly.
Tariq A.
Finance Manager
United Arab Emirates
FAQ
Frequently asked questions
How is this different from OCR-based document validation?
How is this different from the document fraud detection API?
What does a forensic PDF API call return?
What does an inconclusive result mean?
Do I need the original file to compare against?
What documents can the API analyze?
Which single field should my code branch on?
Can another account read my results?
Why did an old result change when I ran the same file again?
How do I retry safely after a timeout?
How long does PDF analysis take?
What happens to my uploaded PDF file after analysis?
How long are analysis results stored?
What is the pricing?
Secure your workflow
Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.