# PDF Tamper Detector (HTPBE, BYOK) (`iurii_rogulia/htpbe-pdf-tamper-detector`) Actor

Checks PDF files for forensic evidence of post-creation modification using the HTPBE API. Bring your own HTPBE API key (free test keys available).

- **URL**: https://apify.com/iurii\_rogulia/htpbe-pdf-tamper-detector.md
- **Developed by:** [Iurii Rogulia](https://apify.com/iurii_rogulia) (community)
- **Categories:** Developer tools, Automation, Integrations
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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](https://htpbe.tech) 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](https://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](https://htpbe.tech/how)
- `modification_confidence`, `usage_caution`, and the rest of the [result schema](https://htpbe.tech/api)

### 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:

```json
{
  "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](https://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](https://htpbe.tech/api) · Docs: [github.com/htpbe/docs](https://github.com/htpbe/docs)

# Actor input Schema

## `apiKey` (type: `string`):

Your HTPBE API key (htpbe\_live\_... or htpbe\_test\_...). Get a free key at https://htpbe.tech/api — this actor brings no checks of its own, it calls your account. Test keys are free and unlimited but only work with the mock URLs at https://api.htpbe.tech/v1/test/\*.pdf.

## `pdfUrls` (type: `array`):

Publicly accessible HTTP/HTTPS URLs of PDF files to check, max 10 MB each.

## Actor input object example

```json
{
  "pdfUrls": [
    "https://api.htpbe.tech/v1/test/modified-high.pdf"
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items — one per PDF URL, with status, modification\_markers, and the full HTPBE result schema.

## `run` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "pdfUrls": [
        "https://api.htpbe.tech/v1/test/modified-high.pdf"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("iurii_rogulia/htpbe-pdf-tamper-detector").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "pdfUrls": ["https://api.htpbe.tech/v1/test/modified-high.pdf"] }

# Run the Actor and wait for it to finish
run = client.actor("iurii_rogulia/htpbe-pdf-tamper-detector").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "pdfUrls": [
    "https://api.htpbe.tech/v1/test/modified-high.pdf"
  ]
}' |
apify call iurii_rogulia/htpbe-pdf-tamper-detector --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,iurii_rogulia/htpbe-pdf-tamper-detector"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BblZGFz3lte5WluZ6/builds/qmEyUN7Ybbd24gDc7/openapi.json