We are very interested in Mindee and are currently evaluating your solution. At the moment, we are using Rossum in production, and we are testing Mindee to compare both platforms and potentially switch if the results are successful. There is one important feature that is currently missing for our workflow: the ability to view documents uploaded via API directly in the Mindee interface, similar to how documents can be reviewed in the Live Test. This capability is very important for our operational and support teams, as it allows easier verification, troubleshooting, and collaboration when processing documents programmatically. We would really appreciate it if this feature could be considered for your roadmap. Thank you for your work and support. Best regards,

vtp 16 days ago

3

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

Ianaré Sévi 20 days ago

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

Ianaré Sévi 20 days ago

We are currently experiencing regular timeout issues when using the enqueue_and_get_inference method from the Mindee Ruby client. Switching to a webhook-based flow would require significant architectural changes on our side, which we would prefer to avoid for now. We noticed in the documentation that it is possible to configure polling_options to increase the timeout duration. However, while investigating how to fine-tune these options, we realized that the GET /v2/jobs/{job_id} endpoint does not return the job createdAt or completedAt timestamps. Without these timestamps, we cannot measure the actual processing time of a job and adjust our polling strategy accurately. Could you please consider adding the following fields to the /v2/jobs/{job_id} response payload? createdAt completedAt Please let us know if this information is already available through another endpoint or if there is a recommended workaround. Thank you in advance for your help !

Faks about 2 months ago

4

Are there any plans to implement detection / a risk rating for fraudulent, tampered or forged documents? This missing piece would hold us back from using Mindee for financial documents, especially since it is rare to find a separate provider that only does fraud detection - most cover some of what Mindee does and also fraud detection. Thanks

Ell Harman about 2 months ago

2

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

Ianaré Sévi 2 months ago

1

Does your receipt OCR API support processing multiple receipts within a single image? If so, will it extract data from each receipt separately or combine them?

FleetYes 2 months ago

3

I'm having trouble having my newly created API KEY recognized, even after having fully followed the technical specifications. i have the following error : Erreur OCR : Erreur technique Mindee : invoices 401 HTTP error: Invalid token provided - Authorization required. Any insights on how to solve this issue ?

Philippe Massoubre expertcomptablenligne 3 months ago

1

Hi Mindee Team, I’m using the Mindee .NET SDK (v3.37.0) in a .NET Framework (net48) application. Our application is strong-name signed, so all referenced assemblies must also be strong-named and contain a valid PublicKeyToken. Currently, the Mindee.dll provided via NuGet is not strong-name signed. Is a strong-named version of Mindee.dll available, or are there any plans to provide one in future releases? Please let us know the recommended approach for environments where strong-name signing is mandatory. Thanks.

Kavya Kavya 3 months ago

8

Hi Mindee Team, I’m using the Mindee V2 API with the C# (.NET) SDK. Is Base64 image input supported directly in V2? In the .NET SDK, I only see LocalInputSource and UrlInputSource. Currently, I have to convert Base64 → file → LocalInputSource. Is this the recommended approach or will direct Base64 support be added? In V2, is modelId the only way to identify invoice, receipt, and passport models? how to differentiate V2 models such as Invoice, Passport and Expense Receipt using the respective modelIds. Thanks.

Kavya Kavya 3 months ago

7

It is really annoying to have to recreate all subfields in a nested field when they already existed as normal fields.

Felix Croizon 4 months ago

3

I’m currently using Mindee to process Russian passports, and I’ve noticed that the extracted name fields are returned in Russian. Could you please advise if it’s possible to receive the name response in English instead of Russian, or guide me on how to configure the API/output to achieve this?

Varsha Aurangabadkar 5 months ago

2

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.

Juan Antonio 5 months ago

4

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

Constance de David Beauregard 6 months ago

2

Update the zapier integration to support v2.

Ianaré Sévi 7 months ago

9

Create an official integration for make.com.

Ianaré Sévi 7 months ago

Hello Mindee Team, I'm currently evaluating your platform with a free trial and I'm very impressed. However, I've run into a confusing issue. The "Live Test" on your website correctly shows polygon coordinates, but this data is missing when using my trial API key. This is made even more confusing because the API settings have an "Include Polygons" toggle. When I try to enable it, I'm blocked by an upgrade prompt. A trial period should be for testing exactly these kinds of core features, but currently, it's impossible to evaluate this functionality. To add to the confusion, your documentation states polygons are available on Pro and Business plans, while the pricing page only lists them for the Business plan, which at 649€/month is extremely expensive and not a viable option for individual developers. This makes the paid Starter plan functionally identical to the Free plan for any developer who requires this feature, offering no real incentive to upgrade. The entire experience makes it impossible to fully test the visual mapping capabilities of your product, which is the critical feature for my decision to subscribe. For personal developer applications, even the Starter plan is quite expensive, and it's unlikely that a developer who needs polygons but not a high volume of requests would subscribe to a Pro or Business plan. My suggestion: Please consider enabling the polygon feature during the free trial period to allow for proper evaluation. Please make polygons available in the Starter plan. This would create a viable upgrade path for individual developers and small projects that need this core feature without requiring the high volume and cost of the Business plan. Thank you for your consideration. Best regards, Felix

Felix Ka 8 months ago

3

Hello, I need to extract elements from a table that may span multiple pages. The table header only appears on the first page. I’ve noticed that the extraction works correctly on the first page, but the model doesn’t seem to recognize the structure consistently on the following pages. I’m not using RAG at the moment because I’m targeting basic, regular invoices. I’d like to know how to solve this issue. I already tried specifying in the schema that the table columns remain consistent across all pages, but this doesn’t seem to improve the results. Could you please help me resolve this issue ? Thank you

Said El haddati 8 months ago

2