Send a financial document, get its data back as structured JSON, and receive a webhook when processing finishes.

What do you need to do?

You need to...Start here
Send your first document and read the JSON backQuickstart
Pull specific fields out of a financial documentExtraction
Know whether a document has been tampered withFraud analysis
Route an incoming file to the right processClassification
Split a PDF that holds several documentsSegmentation
Check a printed address or company number against a referenceField enrichment
Express your own business rules over extracted dataHoloLang
Collect a whole file of documents against one dossierDossiers
Be told when processing finishes, without pollingWebhooks
Know what is safe to retry, and which limits stop a callReliability and limits
Track consumption and processing volumesUsage and Metrics
Run Holofin on behalf of client organizationsSub-organizations

Start building

Three ways in. Pick the one that matches how you work.

Everything starts with an API key from your developer settings. Keys are workspace-scoped and stay active even if the person who created them leaves the workspace.

The API is described by an OpenAPI 3.1 document, which you can feed to a client generator, import into Postman, or hand to an agent alongside the For LLMs files at the top of this page.

Workflows

Everything in Holofin runs through workflows. A workflow is a document processing pipeline that classifies, segments and extracts data from a document in a single API call.

Document
Fraud Analysis
Classify
Segment
Extract
JSON

Configure your workflow once in the dashboard, then trigger it via the API. The workflow handles routing, error handling and the aggregation of results from each step.