In Progress
Fix Webhook Issue in PHP SDK v2 (PHP 8.2+ Compatibility)
I encountered a bug with the PHP SDK v2 where webhook calls were not being received. After inspecting the SDK source code, I found a small issue that appears to be causing the problem. I’ve submitted a pull request with a fix. https://github.com/mindee/mindee-api-php/pull/175/changes/c4baa5459a741a24690145e3bdb13e257f596d90 Could you please review it? Best regards,

vtp About 4 hours ago
🐛 Bug Report
In Progress
Fix Webhook Issue in PHP SDK v2 (PHP 8.2+ Compatibility)
I encountered a bug with the PHP SDK v2 where webhook calls were not being received. After inspecting the SDK source code, I found a small issue that appears to be causing the problem. I’ve submitted a pull request with a fix. https://github.com/mindee/mindee-api-php/pull/175/changes/c4baa5459a741a24690145e3bdb13e257f596d90 Could you please review it? Best regards,

vtp About 4 hours ago
🐛 Bug Report
View API-Uploaded Documents in the Mindee Interface
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 1 day ago
Feature Request
View API-Uploaded Documents in the Mindee Interface
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 1 day ago
Feature Request
Planned
Add PDF merge to Split Model
Allow a user to apply the split page ranges returned by the API to the local file sent.

Ianaré Sévi 5 days ago
Feature Request
Planned
Add PDF merge to Split Model
Allow a user to apply the split page ranges returned by the API to the local file sent.

Ianaré Sévi 5 days ago
Feature Request
Planned
Add image extraction to Crop
Allow a user to apply the crop coordinates returned by the API to the local file sent.

Ianaré Sévi 5 days ago
Feature Request
Planned
Add image extraction to Crop
Allow a user to apply the crop coordinates returned by the API to the local file sent.

Ianaré Sévi 5 days ago
Feature Request
Completed
Taking long time to scan the passport with 2 pages
2 pages passport of INDIAN Passport is taking too much of time to retrieve the information approx 1-2 mins

Varsha Aurangabadkar 13 days ago
🐛 Bug Report
Completed
Taking long time to scan the passport with 2 pages
2 pages passport of INDIAN Passport is taking too much of time to retrieve the information approx 1-2 mins

Varsha Aurangabadkar 13 days ago
🐛 Bug Report
Completed
Add createdAt / completedAt fields in /v2/jobs/{job_id} response payload
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 1 month ago
Feature Request
Completed
Add createdAt / completedAt fields in /v2/jobs/{job_id} response payload
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 1 month ago
Feature Request
Fraud detection
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 1 month ago
Feature Request
Fraud detection
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 1 month ago
Feature Request
Golang client
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 About 2 months ago
Feature Request
Golang client
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 About 2 months ago
Feature Request
In Progress
Multiple Receipts in Single Image Support?
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 About 2 months ago
Feature Request
In Progress
Multiple Receipts in Single Image Support?
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 About 2 months ago
Feature Request
Completed
hello Mindee people :
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 2 months ago
Feature Request
Completed
hello Mindee people :
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 2 months ago
Feature Request
Completed
Strong-Named Mindee.dll & PublicKeyToken Support (.NET SDK)
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 2 months ago
Feature Request
Completed
Strong-Named Mindee.dll & PublicKeyToken Support (.NET SDK)
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 2 months ago
Feature Request
Completed
Base64 Input Support & Model Identification in Mindee V2 (.NET SDK)
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
Feature Request
Completed
Base64 Input Support & Model Identification in Mindee V2 (.NET SDK)
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
Feature Request
Completed
Applicable regulations under the Terms and Conditions of Service
You mentioned your "applicable regulations" under the Terms and Conditions of Service of our Platform or any other master agreement entered into with Mindee. Where can i find your applicable regulations?

Vered Samuel Dalach 3 months ago
Question
Completed
Applicable regulations under the Terms and Conditions of Service
You mentioned your "applicable regulations" under the Terms and Conditions of Service of our Platform or any other master agreement entered into with Mindee. Where can i find your applicable regulations?

Vered Samuel Dalach 3 months ago
Question
In Progress
RAG breaks results
OCR works fine without RAG, but when I add the same document to RAG it now doesn’t work properly.

Felix Croizon 3 months ago
🐛 Bug Report
In Progress
RAG breaks results
OCR works fine without RAG, but when I add the same document to RAG it now doesn’t work properly.

Felix Croizon 3 months ago
🐛 Bug Report
Completed
Move an already existing field to a nested field
It is really annoying to have to recreate all subfields in a nested field when they already existed as normal fields.

Felix Croizon 3 months ago
Feature Request
Completed
Move an already existing field to a nested field
It is really annoying to have to recreate all subfields in a nested field when they already existed as normal fields.

Felix Croizon 3 months ago
Feature Request
Completed
Duplicate items
Mindee is duplicating the lines of the invoices it processes. I've been trying to solve it for hours thinking that it was my app that was generating the error. But I have processed the same invoices from the Mindee website and although the "Extracted fields" part is correct, the JSON does show duplicate lines. Can someone help me to solve this? Thanks.

M4 3 months ago
Question
Completed
Duplicate items
Mindee is duplicating the lines of the invoices it processes. I've been trying to solve it for hours thinking that it was my app that was generating the error. But I have processed the same invoices from the Mindee website and although the "Extracted fields" part is correct, the JSON does show duplicate lines. Can someone help me to solve this? Thanks.

M4 3 months ago
Question
Completed
Any changes to description vs guideline recently?
The model I am using has so far quite reliable extracted supplier domains from documents. I had only a short 1-liner in the description and a more detailed instruction in the guideline. As said it was quite reliable so far. But now I realized that it does not follow this prompt to well anymore – has something changed recently? When I put everything in description it seems to work better but not 100% sure yet. Just want to better understand where to put which instructions so I can optimize. Thx, Roman

Roman Leeb 4 months ago
Question
Completed
Any changes to description vs guideline recently?
The model I am using has so far quite reliable extracted supplier domains from documents. I had only a short 1-liner in the description and a more detailed instruction in the guideline. As said it was quite reliable so far. But now I realized that it does not follow this prompt to well anymore – has something changed recently? When I put everything in description it seems to work better but not 100% sure yet. Just want to better understand where to put which instructions so I can optimize. Thx, Roman

Roman Leeb 4 months ago
Question
Completed
Couldn't deserialize server error
From today we are receiving this in response for our model and file we tested yesterday succesfully ["HTTP -1 - Unknown error :: 000-000 - Couldn't deserialize server error. Found: {\n \"data\": false,\n \"code\": 0\n}"] thrown by MindeeV2HttpUnknownError

Foreo IT 4 months ago
🐛 Bug Report
Completed
Couldn't deserialize server error
From today we are receiving this in response for our model and file we tested yesterday succesfully ["HTTP -1 - Unknown error :: 000-000 - Couldn't deserialize server error. Found: {\n \"data\": false,\n \"code\": 0\n}"] thrown by MindeeV2HttpUnknownError

Foreo IT 4 months ago
🐛 Bug Report