Backlog

Next up

In Progress

Done

Main Roadmap

Provide a client library for integrating the Mindee API using the Go language.Support for:<ul><li>POST using polling and webhook methods</li><li>loading files from various sources (path, bytes, File object, etc)</li><li>PDF splitting before sending</li></ul>Must be able to handle dynamic outputs in a simple way.

In Review

Golang client

Ianaré Sévi

Convert a bundle of documents into CSV. To be able to then upload the document in a financial control system

Possibility to convert and download extracted data to csv.

Constance de David Beauregard

Add the possibility to roll back when I create my model & personalise my data schema

Any proposed solutions for this ?

when using the live interface, I find the zoom rate good on mouse but very fast on trackpad.

Bashir ABDEL WAHED

Today webhooks must be pre-registered per model in the platform UI, and the enqueue call only accepts webhook IDs (<code>webhook_ids</code>). There is no way to give a URL at request time.This does not scale well for us:<ul><li>We have N models and several environments (local, dev, staging, prod), so we have to create and maintain N x M endpoints by hand in the UI, plus one per developer for local work.</li><li>Each environment then needs its own <code>MINDEE_V2_WEBHOOK_ID</code> value to keep in sync, so configuration lives half in your UI and half in our code.</li><li>For local development the tunnel URL (ngrok, localtunnel) changes regularly, so a developer has to go back into the UI and edit the endpoint every time.</li></ul>

[WEBHOOK] Allow an optional callback_url parameter on the enqueue call, as an alternative to webhook_ids

Ismaile ABDALLAH

Hello, I am having a persistent authorization issue while trying to connect to the Invoice OCR API from my <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://n8n.cloud">n8n.cloud</a> workflow.I have already:<ol><li>Confirmed that the "Invoice OCR" model is active in my Mindee dashboard.</li><li>Generated a brand new, clean API key from the "API keys" section of my account.</li><li>Copied this new API key and created a new credential in the official Mindee node in n8n. The node is configured correctly to predict an invoice from a binary file (attachment_0 from a Gmail trigger).</li></ol>Despite these steps, I consistently receive a 401 Unauthorized error with the message "Invalid token provided" every time I execute the node. I have tried generating multiple new keys, and the result is always the same.

n8n integration

Biuro SARCO

We are seeing incorrect results for the supplier name field. The OCR returns the brand name from the page LOGO instead of the legal entity that issued the document.Example: on a receipt the header logo reads "Make", while the actual supplier (legal entity, tied to the address and US EIN 61-1797223) is "Celonis Inc.". The API returns "Make".What we have already tried, without success:<ul><li>Post-processing with a RAG step</li><li>Adding explicit field guidance instructing the model to prefer the legal entity near the address and tax ID and to ignore header logos</li></ul>Neither resolves the issue. The model still favors the visually dominant logo over the legal name in the sender block.Questions:<ol><li>Is there a recommended way to make supplier_name prefer the legal entity (near supplier_address and supplier_company_registrations) instead of the header logo?</li><li>Can this layout be submitted for model review or correction?</li><li>If we annotate sample documents, will that improve extraction for this case?</li></ol>Link to document - https://app.mindee.com/model/701fa3d9-d54b-4e7c-a506-7efed7a5079e/review?docs=98b124b8-2349-4a9a-82c6-6b7699a4a07c File name - 5dea48c8-35ad-4df5-8543-1aa1164691a2.pdfHappy to share sample documents. Thanks for your help.

Supplier name parsed from logo instead of legal entity

Hennadii Shevchyk

Add possibilite de search with model ID

Allow a user to apply the split page ranges returned by the API to the local file sent.

Add PDF merge to Split Model

Allow a user to apply the crop coordinates returned by the API to the local file sent.

Add image extraction to Crop

We are currently facing issues while training documents in RAG.The issues are listed below:<ul><li>Trained documents are not being displayed in the list.</li><li>Pagination is not showing properly.</li><li>When we upload a document in RAG, it does not appear immediately.</li><li>After refreshing the page, the uploaded document becomes visible.</li><li>Once we validate the document, it disappears again from the list.</li></ul>Could you please check this issue and let us know why this is happening?

Issues with RAG Training Documents

Cplus IT

We need to handle scenario where a single, multi-page PDF is automatically split into separate files, each representing a distinct transaction. Use case: Client uploads a batch scan of invoices or receipts. Each transaction can also be multi-page. Example: 50 page PDF containing a mix of single page and multi-page invoices. Some can have attachments.The resulting split should ALWAYS start with 1st page of invoice. If there are attachments, these do not need to be split apart and can be part of the resulting transaction. In our experience, each invoice starts with Invoice page 1 and hence that can serve as an indicator where to split the file.

Completed

PDF Content Splitter - split multipage PDF into individual Invoices/Receipts

Jan Korecky

It would be helpful to include the coordinates of the bounding boxes for each extracted field in the output. This would allow us to visually highlight extracted data on the original document, improving validation, debugging, and user interface capabilities. When reviewing extracted fields in our UI, having the ability to draw boxes around the relevant text on the document would enhance the user experience and make it easier to verify extraction accuracy.

Add bounding boxes to extracted fields

Adèle LIBMAN

Hi, We would like a feature that allows us to retrieve a picture from a resume that has been sent to analyze via API. The best option would be to have, in the list of extracted data from the “Resume OCR”, a new element : { "image": [ {“type”: “picture|logo|other”, "id": "document_unique_id", '“dimension”: “widthXheight”, “location”:”coordinates” } ] }<ul><li>type : would describe the type of images ; eventually this could also be added as a filter in the OCR request</li><li>document_unique_id : would be the id of the extracted document, available for download via Mindee API</li><li>widthXheight : the dimensions of the picture, width by height, for example “150×450”</li><li>coordinates : the abscisse and ordinates of the pictures in the original documented, for example “ 300;100”</li></ul>The coordinates would be usable by ImageMagick.Thanks

Extract picture and images

Mansuy DEJEAN

When the image or document contains barcodes or QR codes in addition to text or photos, it should interpret them and returns their values, not just the object's coordinates. This would be useful for scanning tickets, boarding passes, and all documents that have barcodes to be read.<img data-width="100%" data-align="left" data-featurebase-content-key="682f69c9e2404756e7e68d15/post/68ff565199e5f1a4bde63182/019a2568-4192-778b-864d-f6e4291134ad/b64u-MTAtMjctMjAyNV8xMl8yMl9QTS5wbmc.png" data-featurebase-content-filename="10-27-2025_12_22_PM.png" src="https://682f69c9e2404756e7e68d15.featurebase-attachments.com/c/post/68ff565199e5f1a4bde63182/019a2568-4192-778b-864d-f6e4291134ad/b64u-MTAtMjctMjAyNV8xMl8yMl9QTS5wbmc.png?X-Amz-Expires=3600&amp;X-Amz-Date=20260823T220000Z&amp;X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=DO801TYC4FCVNNEKURKM%2F20260823%2Ffra1%2Fs3%2Faws4_request&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=fad8b76e4f9750b578d390b556da2e85b3c3a3c262aa93cfb7735c6128deb9ae">

QR / Barcode value decode

Juan Antonio

Update the zapier integration to support v2.

Zapier integration

My API key is returning '401 Unauthorized - Invalid token provided' when making parse requests to the InternationalIdV2 endpoint. The client initializes successfully and document creation works, but all parse calls fail with authorization errors. Anything I should Optimized? thanks

API Error

Romain Colineaux

Provide a client library for integrating the Mindee API using the Ruby language.Support for:<ul><li>inference using polling and webhook methods</li><li>loading files from various sources (path, bytes, <code>File</code> object, etc)</li><li>PDF splitting before sending</li></ul>Must be able to handle dynamic outputs in a simple way.

High Priority

Ruby Client Library

I’m working with a 16-page credit score report, but the information I need to extract is located only on page 8. It would be extremely useful to have the ability to target a specific page for parsing and extraction, rather than processing the entire document.

Page-Specific Data Extraction

I need to know when the models are sure of what they extract. I’d need a confidence score associated to each extracted value in the JSON

Add confidence score

keith.mt112

Hey! It would be great to see the live test and be able to modify the data schema on the same page. Tedious to do back and forth between the two tabs every time.