Changelog

Webhooks now require a Business or Enterprise plan. Registering an endpoint, editing one, rotating its secret and sending a test all need the feature. If your plan stops including it, deliveries stop, but your endpoints stay listed so you can still remove them.

An organisation may register up to 10 webhook endpoints. Adding another is refused until you delete one — every endpoint multiplies the requests we make for each document you process.

A webhook URL must resolve to a public address. An endpoint pointed at a private, loopback or link-local host is refused when you save it, and checked again before every delivery — so a hostname re-pointed inward later stops being delivered to rather than retried.

Webhooks. Register an endpoint under Webhooks to receive signed `document.processed` and `document.failed` events. Every delivery carries an `X-Heirs-Signature` header you can verify with your endpoint's signing secret — see the API reference for the verification snippet.

Request Logs. Every API call your organisation makes, including the ones that were refused — over quota, rate limited, unsupported file type. These never appear under Documents, so this is the place to debug a failing integration.

Backup. Download a copy of your documents, API key metadata and team as JSON. It is an export for your records, not a restore point — key secrets and passwords are deliberately unrecoverable and are not included.

Job Queues. Large documents are processed in the background; this page shows their status, duration and retry count while they run.

Two-factor authentication. Enable TOTP under Security. Once enabled, signing in requires a code from your authenticator app — a password alone will not establish a session. Enrolment issues ten single-use recovery codes; store them somewhere safe, as they are shown only once.

Active sessions. See where your account is signed in, and sign out every other device at once. Changing your password now also revokes all other sessions.

IP allowlist. Owners can restrict portal sign-ins to specific addresses or CIDR ranges. Existing sessions are unaffected, and a list that would lock you out is rejected rather than saved.

Documents and Reports. Every document processed through a standard function is listed with its outcome, page count and duration, with a trailing-window report. Documents run through identity and other PII functions are never recorded — not even their filenames — so this list is deliberately not a complete account of everything you submitted. Billing remains the authoritative usage total.

API key expiry. Keys can be minted with an expiry date, after which they stop authenticating but remain visible in the list as expired.

API keys now follow a consistent `hok_live_…` / `hok_test_…` pattern. Existing keys continue to work unchanged.

Billing & Usage. Your current plan, documents and pages processed this period, accrued charges, and the plan's limits.

Runs started from the portal's OCR page are now attributed to your organisation, so in-app usage counts toward the same totals as direct API calls.