Welcome to the guide section of Ocrolus, where we'll explore how this platform can help you optimize your workflows for processing financial documents. This guide will provide a detailed understanding of how Ocrolus works and how it can benefit your organization.

Ocrolus provides an API that seamlessly classifies documents, captures key data fields, detects fraud, and analyzes cash flows and income. In the following sections, we'll explain each step of the process in detail:

Classify

Using advanced machine learning algorithms, Ocrolus can quickly recognize and categorize your documents. In case of any uncertainties, our system automatically routes the document to Ocrolus verifiers for human review, ensuring the highest level of accuracy. To learn more about Classify, see Classify product guide and API reference documentation.

Capture

Ocrolus extracts data from your document and returns the data to you in a structured format, eliminating the need for manual entry and validation. This significantly reduces labor hours and accelerates the processing time from end to end. To learn more about Capture, see Capture product guide and API reference documentation.

Detect

Ocrolus checks qualifying documents for signs of suspicious activity, such as file tampering, incomplete data sets, missing pages, invalid dates and amounts, abnormal fonts, and irregular formats. Our fraud detection algorithms work around the clock to keep your financial documents secure. To learn more about Detect, see Detect product guide and API reference documentation.

Analyze

Ocrolus helps you gain deep insights into borrower cash flows and income with clean, normalized data. It allows you to make informed decisions for your business with ease by analyzing financial data. To learn more about Analyze, see Analyze product guide and API reference documentation.

Ocrolus API reference

The Ocrolus API is a simple and secure HTTP API that accepts JSON payloads as input parameters and returns actionable data in JSON format.

📘

Notes:

• The majority of Ocrolus endpoints returns data in JSON format. It's important to note that JSON keys can appear in any sequence, resulting in potential differences between the object order in the example responses within the API Reference and those encountered in actual practice. Such variations are entirely expected and should be considered normal.
• New fields may be introduced to objects in our endpoint responses at any time. See our policy on Breaking Changes for additional information.
• While the Ocrolus API uses HTTP transport, we do not currently leverage HTTP status codes to report error conditions outside of a limited set of site-wide issues. For more details about HTTP status codes, see HTTP status codes.

Whether you're new to the Ocrolus API or refreshing your knowledge, this is where you'll find the necessary information to automate document processing with Ocrolus.

We recommend that you pay particular attention to the various endpoints supported by our API, along with the input parameters and the different interaction modes of these endpoints.

Unless otherwise stated, we only support North American documents at this time.