Overview

The Fileverity API lets your software check images, documents and plain text with Fileverity models. One API key and one prepaid workspace balance cover every model. Image and document results are the same reports the website produces, each with a report ID, an RFC 3161 timestamp and a public verification page.

New here? Follow the Quickstart to make your first call in a few minutes, or get a test key and call the API right away. For a product overview, see the API page, the AI image detection API and the Document fraud detection API.

Models#

Prices, limits and snapshot IDs are listed on Pricing and billing.

Conventions#

• Base URL. https://api.fileverity.com/v1. HTTPS only.
• Format. Requests are JSON, except file uploads, which are multipart. Responses are JSON, except the PDF report. Timestamps are Unix seconds, except inside result.report, where times are ISO 8601 in UTC.
• Authentication. A bearer API key in the Authorization header. See Authentication and keys.
• IDs. Objects carry a prefix: file_ files, an_ analyses, tdet_ text detections, evt_ webhook events, req_ requests. Report IDs look like FV-XXXX-XXXX-XXXX.
• Request IDs. Every response has an x-request-id header, and every error repeats it as error.request_id. Quote it when you contact support.
• Checks, analyses and reports. A check is what you run and pay for: an image check, a document check or a text check. In the API, an analysis is one image or document check, and a text detection is one text check. Image and document checks produce a full report; a text check produces a result.
• Versioning. The version is in the URL. New fields and endpoints can be added to v1, so ignore fields you do not recognize. A model ID such as fvimg-2 points to a dated snapshot (fvimg-2-2026-10-30). Results report the snapshot that produced them, and you can pin a request to a snapshot by passing its ID as model.
• Languages. Text detection accepts en, fr, de, es, zh.

OpenAPI specification#

The API is described by an OpenAPI 3.1 document at https://api.fileverity.com/v1/openapi.json. The API reference is generated from that document, so the two always agree. The document can be loaded from a browser, so tools such as Swagger UI and Postman can import it by URL, and GET https://api.fileverity.com/v1 returns links to these docs and to the specification.

What is in these docs#

• Quickstart: from sign-up to a first result.
• Authentication and keys: live and test keys, revocation and spend limits.
• Text detections, Files and Analyses: the ways to run a check.
• Webhooks and Idempotency: production behavior.
• Sample code: complete Node.js and Python programs for each check and for webhooks.
• Document checks in an intake workflow: upload, webhook, routing by risk level, human review and later verification.
• Errors and Rate limits and headers.
• Pricing and billing and Data retention and security.
• Changelog and the API reference.

The same checks in the browser#

You do not need the API to run a check. The website offers Check an image, Document verification and Image verification, and the Console runs all three checks against your workspace balance.

Support#

Write to hello@fileverity.com or use the contact page, and include the request ID (x-request-id), the time in UTC and the endpoint. Temporary failures return 503 service_unavailable with a retry-after header and are never charged. Need higher limits or volume pricing? Contact sales.

Reading these docs with an agent#

Every page is also available as Markdown: add .md to its path, for example /en/docs/quickstart.md. The index of all pages is at /en/docs/llms.txt.