Menu

Test Keys & Deterministic Scenarios for PDF Tamper Detection
📰

Test Keys & Deterministic Scenarios for PDF Tamper Detection

DEV Community: api·Iurii Rogulia·19 days ago
#eK2Sj68h
#devtoapi#devto#dev#test#live
Reading 0:00
15s threshold

Originally published at htpbe.tech . The version on htpbe.tech stays in sync with the latest detection algorithm — refer to it for the canonical text.

An HTPBE test key (prefix htpbe_test_ ) accepts only the documented test URLs, https://api.htpbe.tech/v1/test/{name}.pdf . It downloads nothing: each name maps to a built-in, deterministic result with a fixed check ID, and no credits are spent. That makes the whole flow – POST /v1/analyze , then GET /v1/result/{id} – stable enough to run in CI on every pull request.

HTPBE is PDF tamper detection: it reports whether a file’s structure shows evidence of modification after it was created. It does not verify identity, issuer records or what the document says, and nothing about test keys changes that.

This article is about the test suite around your integration: which scenarios to use for which code path, what to assert, which error paths you can and cannot reach, and how to split test and live keys in CI.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.