Invofox vs Mindee API

Invofox

Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise.

Mindee API

Extracted data kept 12 hours by default (1 to 24 configurable), deletable on fetch, source files never stored. Every call needs a model_id created in the web platform first.

Invofox

1. Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types
2. Upload with POST /v1/ingest/uploads as multipart, with info as a JSON string. Send "useClassifier": true in place of type to have the type detected
3. Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded
4. Handle the file.rejected webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely
5. Do not retry an upload blindly. There is no idempotency key, so send your own id in clientData and look it up with filter first

Mindee API

1. Create the model in the Mindee app and store its model_id; the API can't create one for you
2. Enqueue returns 202; poll the job or use a webhook, and keep polling under 1,200 a minute
3. Send Authorization: $MINDEE_API_KEY with no Bearer prefix
4. Turn on confidence scores only when needed, since they cost 1.5 credits a page instead of 1
5. Keep schemas to 25 fields or fewer, the documented recommendation