Changelog

AI Review now localizes individual lines and words in the document as evidence. Previously we only identified entire sections. You can now speed through reviews by focusing on the most relevant parts of the document.

Confidence estimates in AI reviews are now significantly more accurate, allowing you to build workflows that focus on low-confidence items.

AI Review now supports a human-in-the-loop editing. You can now add, change, and remove values in the review interface, and set an official "verified" status for items. This supports flows that require human validation of AI results, such as in legal or compliance contexts.

We're still focusing our attention on making review workflows more useful. Please reach out to customer support if you run into any issues or have a feature request to make review capabilities more useful to you.

AI Review has been completely overhauled! AI review lets you see where in a document results came from.

Features include: handling of very long documents and thousands of standardization items. You also get much more precise localization, and vastly improved reliability

Review now lets all users change, remove, and add values, as well as set an official "finalized" state.

This allows you to seamlessly build human-backed pipelines that can be used to validate results, improving your document reviewing humans 10x faster than before.

Standardization V2.2 will become the new default on the API in one week, on June 12, 2025. This version has been available for a while now, and we have received positive feedback from users. It is faster and more accurate than the previous version, and we encourage everyone to try it out. There might be several final tweaks before stabilization as the new default. To use a previous version, simply set stdVersion=2.0 or 2.1 in the API.

Standardization V2.2 has been released on both the website and API. No interface or parameter changes, but the model has been improved to better handle complex documents and edge cases, and should generally produce more accurate results. The default version on the API is still V2.1, but you can select the new version explicitly by setting stdVersion=2.2. The website is now using V2.2 by default.

Expanded file‑format support – Tables (.csv, .xls, .xlsx) uploads are now supported via both the website and API. Table files are parsed natively and do not consume parsing credits.

DocuPipe now supports larger document uploads. The new maximum file size is 2GB (up from 1GB), and the maximum number of pages is 1000 (up from 500). This change is available via both the website and the API. We still recommend exercising caution when standardizing large documents, as job failures are more likely.

Analysis results are now viewable from the Jobs tab instead of needing to navigate to the Analysis tab.

Document viewer now has zoom control, to allow for easier reading of documents. Quality of life!

We’ve officially rebranded from DocuPanda to DocuPipe. There’s no impact on service – all existing functionality remains the same. The only change is that our website and API endpoints now use docupipe.ai. The previous API URL (app.docupanda.io) will continue to work without changes. We’re excited to continue evolving under our new name and bring you even more powerful features ahead.

We’ve entered the 3-month observation period for our SOC 2 Type II audit and expect full certification by August 2025. Security and privacy have always been core to DocuPipe, and this milestone underscores our ongoing commitment to maintaining the highest standards.

Accordingly, our Trust Center has been updated to reflect this change. You can find the new Trust Center at https://trust.docupipe.ai. This page provides very comprehensive information about our security and privacy practices and tech stack.

When uploading a PDF, you can now specify the page range to be parsed. This is useful if you only want to upload a specific subset of pages, and only get charged credits for those pages.

It is now possible to standardize without a schema from the website (previously it was only possible via the API). This is useful if you want to standardize a document without having to create a schema first. The schema will be created automatically based on the document content and the custom instructions (guidelines).

Split now has two additional quality-of-life input parameters: dataset and filename prefix. Both of these new arguments are optional, and leaving them blank keeps the previous behavior. The dataset parameter allows you to assign a new dataset value to any documents generated from the Split job, and the filename prefix parameter allows you to control what prefix will be given to newly generated files (the suffix is still determined by the AI, as before).

Standardize V2.1 released.

The only difference is that fields which weren't found are now an explicit null. For example, we will produce {"rentAmount": null} where before we used to omit rentAmount alltogether if not found.

Scheduled Change: Version 2.1 will become default for all API users and website visitors. This will happen April 23, 2025.

If you must retain the old behavior, you can set stdVersion=2.0 in the API.

Expanded file‑format support – Word (.doc, .docx), HTML, plain text, and JSON uploads are now supported via both the website and API. Word and HTML files are converted to PDF; plain text and JSON files are parsed natively and do not consume parsing credits. Excel support is coming soon.

Parallel batch processing: Standardize batch jobs now execute documents in parallel instead of sequentially, significantly reducing overall processing time.

The promotion period for high effort level standardization ends April 23, 2025. From that date, setting effortLevel='high' will be charged 4 credits per page. This is double the standard rate of 2 credits per standardization.

The promotion period for review action ends April 23, 2024. From that date onwards, the review action will be charged 2 credit per page. This was previously free for our beta users.

Standardization V2 is now the new default in the website. We will continue supporting all versions on the API and website, but encourage users to try the new version. It will continue improving in the coming weeks, and we appreciate the feedback we have been getting from users to help improve it and make it even better.

The document viewer in the website has received a makeover, allowing you to more seamlessly move between viewing your document, text results, and standardizations. We hope you enjoy!

Uploading documents now auto-suggests relevant schemas based on the document type, allowing for a more streamlined flow.

The cost of schema creation and refinement has been reduced from 2 credits per page to 1 credit per page. We think this will let users feel more free to create more schemas and iterate on them in the Improve tab.

The cost of classification has been reduced from 1 credit per document, to 0.1 credit per page (rounded up), as this is more fair for most users.

The cost of analyze has been reduced to 0.5 credit per page (rounded up), and has been simplified into a uniform pricing regardless of whether you are analyzing a single document or multiple documents. The behavior has also changed to be more verbose.

We are pleased to announce that Standardization V2 has been released! It is available via both the website and the API. The new version is faster, more accurate, and more flexible than the previous one. However, it might not immediately work better for everyone, and V1 is still available and will remain the default on the website for a while longer. From the API, Standardization V2 has a separate endpoint: /v2/standardize/batch (see API docs for details). Also see a new article on Standardization in the Help Center that explains a bit about how the new version works, and what its input parameters are for. Please start experimenting with V2 and give us feedback, it will still be improving over the next weeks before the launch is finalized and it becomes the new default.

The parsing model has been upgraded to V2 in the API (in addition to the website). The POST /document endpoint accepts an optional parseVersion parameter, which can be set to 1 or 2 (default is now 2).

We have improved how we spatially display documents to the AI in standardization and analysis, which should improve results.

Standardizations can now be downloaded as Excel files from the API as well, under the endpoint /standardization/{standardization_id}/download/excel-url, which gives you a temporary URL to download the Excel file. This feature is free of charge.

The parsing model has been upgraded to a new version (V2), which improves accuracy with tables, checkmarks, and handwriting recognition. This update is now the default on the website and will become the default in the API in one week. The POST /document endpoint now accepts an optional parseVersion parameter, which can be set to 1 or 2. The default remains 1 for now but will switch to 2 in one week. To continue using the old version, set parseVersion to 1.

We added an ability to download individual standardizations as an Excel file. This feature is currently available only via the website, under the Standardization tab: click Download -> Excel. The Excel file will contain the same information as the standardization details page, but in a more structured format: non-array fields will be in a sheet called 'main', and array fields will be in separate sheets named after the array field. This feature is free of charge, and will be available in the API soon.

In document parsing, we removed the underscore padding in tables, as it caused issues with some documents. Newly parsed documents will revert to the previous behavior of having empty table cells filled with a simple empty string. For standardization with standardizationMode='sectionBased', we will still use padding to improve results.

You can now right-click tabs in the dashboard menu for opening a new tab (this was not possible before).

We have disabled the mobile view for the dashboard, as it was not optimized for mobile devices and caused issues.

We added an API endpoint to POST a new schema from scratch. Up until now, a schema could only be updated from an existing schema, but now you can add a schema object directly using the API. The endpoint is POST /schema - find more details in the API docs.

A bug was fixed where previously we allowed schemas to have fields with type=enum, which is not a valid type in JSON Schemas (enum is an additional key in a field, not a type). We only allow the types 'string', 'number', 'integer', 'boolean', 'object', 'array'.

Added the ability to download a PDF with the OCR layer baked in. Available both in the API at the endpoint document/{document_id}/download/ocr-url or via the website, under the Documents tab: click Download -> File (OCR Layer). In further detail, this feature allows you to download your PDF - which may be handwritten or contain images - with DocuPipe's OCR layer placed on top of the document in invisible font on the word level. This allows you to search your PDF, or highlight / copy text from it, even if the original document was just a scan. This service is free of charge.

In document parsing, we added underscore padding in tables (instead of empty string), which improves readability / rendering and standardization results, as it makes it easier for the AI to keep track of table columns. This affects anyone using the document.result.text output in its raw form, or anyone using standardization with standardizationMode='sectionBased'.