Help us improve!

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

In Progress

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 7 days ago

3

Completed

Make Polygons Available in Free Trial and Starter Plan

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

3

In Progress

n8n integration

Hello, I am having a persistent authorization issue while trying to connect to the Invoice OCR API from my n8n.cloud workflow. I have already: Confirmed that the "Invoice OCR" model is active in my Mindee dashboard. Generated a brand new, clean API key from the "API keys" section of my account. 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). 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.

Biuro SARCO 7 months ago

15