On the Billing page, when I try to downgrade, the downgrade preview fails to load. I see the message: “Failed to load downgrade preview” and “Failed to calculate plan change cost”. I can click “Retry”, but the preview still does not appear, so I cannot confirm the downgrade.
We are seeing incorrect results for the supplier name field. The OCR returns the brand name from the page LOGO instead of the legal entity that issued the document. Example: on a receipt the header logo reads "Make", while the actual supplier (legal entity, tied to the address and US EIN 61-1797223) is "Celonis Inc.". The API returns "Make". What we have already tried, without success: Post-processing with a RAG step Adding explicit field guidance instructing the model to prefer the legal entity near the address and tax ID and to ignore header logos Neither resolves the issue. The model still favors the visually dominant logo over the legal name in the sender block. Questions: Is there a recommended way to make supplier_name prefer the legal entity (near supplier_address and supplier_company_registrations) instead of the header logo? Can this layout be submitted for model review or correction? If we annotate sample documents, will that improve extraction for this case? Link to document - https://app.mindee.com/model/701fa3d9-d54b-4e7c-a506-7efed7a5079e/review?docs=98b124b8-2349-4a9a-82c6-6b7699a4a07c File name - 5dea48c8-35ad-4df5-8543-1aa1164691a2.pdf Happy to share sample documents. Thanks for your help.
When upgrading to Starter / Pro / Business, there is currently no option to enter an EU VAT number for company purchases, meaning VAT is always included in the final amount instead of being exempted for eligible EU VAT-registered companies.
We are currently facing issues while training documents in RAG. The issues are listed below: Trained documents are not being displayed in the list. Pagination is not showing properly. When we upload a document in RAG, it does not appear immediately. After refreshing the page, the uploaded document becomes visible. Once we validate the document, it disappears again from the list. Could you please check this issue and let us know why this is happening?
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,
2 pages passport of INDIAN Passport is taking too much of time to retrieve the information approx 1-2 mins
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
Hi there, anyone else having issues updating instructions? When I click save nothing happens, can’t update a models instruction for a given field in the data schema. Here’s a loom: https://www.loom.com/share/8b6dea47be8148f695cf29f5e0c32dcc Tried logging in and out, clearing cookies - happening on both Chrome and Firefox. Would appreciate if someone could let me know how to solve this. Thx, Roman
Hello again! When I try to add a row in the RAG document review, the page doesn’t load. The browser console shows the following: I am using Firefox, but I also tested in Chrome and it happen again I can add guidelines, but when I click on the row button, the page turns black and doesn’t display anything. This happened yesterday, after I delete a document from the RAG and created a new one. However, I haven’t made any change to this for a while, so I don’t know it’s related to this. Best regards
Hello! When we tray t execute API call API https://api-v2.mindee.net/v2/inferences/enqueue with the Model_id 'b0f84468-d7bd-49c8-8818-eec5f01d3e9c' we get the following error, that 3 days ago when we migrated from V1 to V2 didn’t occured: { "statusCode": 500, "headers": { "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "x-ms-environment-id": "default-172d5c03-04d9-45ba-adb5-b6d7b8f02e6a", "x-ms-tenant-id": "172d5c03-04d9-45ba-adb5-b6d7b8f02e6a", "x-ms-dlp-re": "-|-", "x-ms-dlp-gu": "-|-", "x-ms-dlp-ef": "-|-/-|-|-", "x-ms-apihub-cached-response": "false", "x-ms-apihub-obo": "false", "Date": "Wed, 29 Oct 2025 15:42:46 GMT", "Content-Length": "123", "Content-Type": "application/json" }, "body": { "status": 500, "detail": "An unexpected server error occurred.", "title": "Internal Server Error", "code": "500-003", "errors": [] } } Thank you
Hi Mindee team 👋 I’m integrating the Mindee OCR API inside a NestJS backend (running in Docker), and I’m getting a consistent HTTP 422 - Empty file sent error when using Base64Input with the V2 client. 🧩 Code example this.client = new mindee.ClientV2({ apiKey: config.apiKey, }); async parseReceipt(imageBase64: string): Promise { const inputSource = new mindee.Base64Input({ inputString: imageBase64, filename: 'receipt.jpg', }); // I also tried manually initializing: // await inputSource.init(); // The Buffer is correctly filled here. const apiResponse = await this.client.enqueueAndGetInference( inputSource, { modelId: this.modelId, rawText: true, } ); return {}; } ⚙️ Context SDK: mindee (latest, ClientV2) Environment: NestJS (Node 20, Docker) Model: Input: Base64-encoded JPEG (I confirmed it’s valid and decodes properly) 🧠 What I noticed Even when I manually run await inputSource.init(), the inputSource.buffer is correctly filled with the decoded image data. However, as soon as I call: await this.client.enqueueAndGetInference(inputSource, { modelId: this.modelId }) the SDK still throws: MindeeHttpErrorV2: HTTP 422 - Empty file sent. 🙏 Question Is there something I’m missing when using Base64Input with ClientV2? Does it need a specific encoding format or initialization step before sending? Thanks for your help!
I'm focused on helping with document extraction. Could you please clarify what fields you'd like to extract from your documents? Everytime this reply at everything.
Hello, cant create model with assistant however i said. Since yesterday.
Good morning, last night we got a 500 error on all the documents sent. This morning I tried again and it gives the same error, I’m attaching it below. { "statusCode": 500, "headers": { "Date": "Fri, 03 Oct 2025 00:33:48 GMT", "Connection": "keep-alive", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "Content-Type": "application/json", "Content-Length": "62" }, "body": { "status": 500, "detail": "An unexpected server error occurred." } } { "statusCode": 500, "headers": { "Date": "Fri, 03 Oct 2025 07:28:59 GMT", "Connection": "keep-alive", "Strict-Transport-Security": "max-age=31536000; includeSubDomains", "Content-Type": "application/json", "Content-Length": "62" }, "body": { "status": 500, "detail": "An unexpected server error occurred." } }
Hi! The document review form resets always I change the window. It’s very annoying because I want to copy data from the document and I can’t. Here you have a link to a loom video reproducing the issue: https://www.loom.com/share/5599fc6ea1494b8285bb3686c87a7ab3?sid=e6bcf3e2-3d8d-4834-8564-d8dab2aaf749
Hi Mindee team, I’m integrating the expense_receipts model via the V2 API from a Supabase Edge Function and I’m consistently receiving 401 Unauthorized. Endpoint being called POST https://api.mindee.net/v1/products/mindee/expense_receipts/v5.3/predict Authorization: Token md_******************** Content-Type: image/jpeg Accept: application/json (body: raw JPEG bytes) What I’ve verified Using a V2 key (prefix md_…), trimmed (no whitespace/newlines). Same key tested via curl returns 401 as well. Model path uses path segment versioning (/v5.3/), not @v5.3. Also tried predict_async; falls back to predict when not supported. Content types tried: image/jpeg and image/png. No proxy; requests originate from Supabase Edge (Deno) and from local curl. Recent logs (redacted) Mindee base: https://api.mindee.net/v1/products/mindee/expense_receipts/v5.3 Mindee response (sync) 401 Mindee error 401 … Questions / help requested Is the expense_receipts v5.3 public model accessible with standard V2 keys, or is a specific entitlement/workspace toggle required? Do V2 keys need to be created inside the same workspace/project where the receipts model is enabled? (Could a key from another workspace cause 401?) Can you confirm the correct product path for the receipts model in V2 (/v1/products/mindee/expense_receipts/v5.3/predict) and that raw binary (not multipart) with Content-Type: image/jpeg is acceptable? Are there any IP restrictions or organization settings that would return 401 instead of 403? If possible, could you check this key’s scope/status on your side (last 24h) to see why auth fails? Repro with curl export MINDEE_API_KEY='md_xxxREDACTEDxxx' curl -i -X POST \ -H "Authorization: Token $MINDEE_API_KEY" \ -H "Content-Type: image/jpeg" \ -H "Accept: application/json" \ --data-binary @sample.jpg \ "https://api.mindee.net/v1/products/mindee/expense_receipts/v5.3/predict" Thank you! Happy to provide full timestamps, workspace name, and any additional headers privately if that helps you trace the request.
Good morning, We have a flow in Power Automate from which we send the documents to be processed. Then we have another flow with a webhook where the document is sent. The issue is that since last night, we are not receiving all the responses to the webhook. Out of 23 documents sent last night, we only received the response for 2. I thought it might be due to too many API calls per second (although I haven’t received any errors, and in subsequent submissions I do receive a 202 response for all documents), so I added a 15-second delay between each call. In the first batch sent a little while ago, we received responses for 4 documents, in the next batch 4 more, then 6, and in the last one 7. I also want to point out that in the web panel the number of processed pages is increasing, so the documents seem to be processed, but the webhook responses are not always being received. This has never happened to us before. Could you please let me know if there is any kind of issue or limitation with the webhooks on your side? Thank you, Best regards