Have something to say?

Tell us how we could make the product more useful to you.

Note that this feedback section only concerns Mindee V2:

https://app.mindee.com and https://api-v2.mindee.net/

Completed

Clarifying questions before evaluation

Hi there I have only spend 30 min. on reading about Mindee, but I hope it is ok that I already ask questons now. On behalf of a client I need to find a tool that is strong on OCR reading complex line item scenarios. Our initial project is load of purchase orders and later will try with invoices and inventory documents. And if that turns out to be successful, we will probably find other scenarios. Our coding will be SAP ABAP. Questions: 1) I have read the “Data Processing Agreement”, but I am a technician and as always I find the legal stuff to be written in gibberish. We would for sure start out with the Starter plan, but on the Organisation and Members page I can see that it is not possible to set the Default Processing Zone to Europe unless I have at least the PRO plan. My client is based in UK and EU and it is a requirement that no data leaves Europe. Is it guaranteed that no data leaves Europe? 2) I guess ABAP programming is what you call manual integration and in documentation you say “We do not recommend manually integrating”, but do know if you have customers that built the API calls in ABAP? 3) We expect a flow like a) OAUTH for authentication and get token b) REST API call to select schema and upload PDF c) Rest API call in poll loop until success or fail Is this a normal/possible flow? Best regards Thomas Madsen Nielsen

Thomas Madsen Nielsen 28 days ago

4

Question

Completed

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 2 months ago

3
💡

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 3 months ago

4
💡

Feature Request