Enable confidence score calculation for Split Model chained with extraction Model

We would like to know if it is possible to enable confidence score calculation when using a Split Model chained with an Extraction Model. Currently, when an Extraction Model is chained after a Split Model, there is no way to enable confidence score calculation for the Extraction Model results. Expected behavior We would like to have an option to enable confidence score calculation for the Extraction Model when it is used in a chain with a Split Model. Question Is there currently a configuration or option that allows us to enable confidence score calculation for this use case? If not, could this capability be considered for a future release? Thank you.

Add possibilite de search with model ID

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

Today webhooks must be pre-registered per model in the platform UI, and the enqueue call only accepts webhook IDs (webhook_ids). There is no way to give a URL at request time. This does not scale well for us: 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. Each environment then needs its own MINDEE_V2_WEBHOOK_ID value to keep in sync, so configuration lives half in your UI and half in our code. 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.

Bonjour

MINDEE peut-il récupérer en automatique les factures PDF sur un mail ou une plateforme de factures?

Allow unlocking a model via a button

The Lock feature exists to improve security. But when we need to edit a locked model, the only option is to duplicate it and switch internally, which actually adds risk (parallel versions, wrong switch, lost traceability). Request: Allow models to be unlocked. An explicit, tracked unlock would be safer than the current duplication workaround

Allow updating the storage policy while a model is locked

Currently, when a model is locked, the storage policy field becomes read-only and cannot be modified. This restriction doesn't seem necessary, updating the storage policy shouldn't have any impact on a locked model's integrity or behaviour.

I am considering switching to an annual subscription. I have recently started a new business, and my budget is currently limited. Would it be possible to receive a promotional code or a small discount to help me with the annual subscription cost? I would really appreciate your support.

how to download extract data

i juste see a json file, ther is no other solution ? (excel,cvs,text or other ?) thanks

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,

Add PDF merge to Split Model

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

Add image extraction to Crop

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

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 !

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

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.

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?

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 ?

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.

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.

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.

Request for English Name Extraction for Russian Passport

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?