> For the complete documentation index, see [llms.txt](https://docs.mindee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mindee.com/integrations/technical-limitations.md).

# Technical Limitations

Technical limitations when integrating Mindee.

These limitations are designed to ensure the safety and stability of the Mindee API and platform.

Unless noted otherwise, any action that exceeds or does not comply with the limitations will be rejected with an error.

## Accepted Files

### PDF Files

All Portable Document Format (PDF) can be processed, either single page or multiple pages.

These are defined using the `application/pdf` Media type.

In some cases `application/binary` is used, this is incorrect as per the standard, but should also work, so long as the extension is `.pdf` and the binary contents are a valid PDF file.

In rare cases, the PDF headers are corrupted or invalid. Fix these using our [PDF repair tool](/integrations/client-libraries-sdk/load-and-adjust-a-file.md#fix-pdf-headers), otherwise the server may reject them.

Each PDF page can be a combination of text and image elements.

{% hint style="warning" %}
**PDF files cannot be password-protected.**

The server will not attempt to open a password-protected file, so this limitation includes empty or blank passwords.
{% endhint %}

### Image Files

Most common image types can be processed.

Specifically, we accept the following image types:

<table><thead><tr><th width="140">Type</th><th width="158.5">Media Type</th><th width="135.5">Extensions</th><th>Notes</th></tr></thead><tbody><tr><td><a data-footnote-ref href="#user-content-fn-1">JPEG</a></td><td>image/jpeg</td><td>jpeg, jpg</td><td></td></tr><tr><td><a data-footnote-ref href="#user-content-fn-2">PNG</a></td><td>image/png</td><td>png</td><td>non-animated only</td></tr><tr><td>WebP</td><td>image/webp</td><td>webp</td><td></td></tr><tr><td><a data-footnote-ref href="#user-content-fn-3">TIFF</a></td><td>image/tiff</td><td>tiff, tif</td><td>single page or multiple pages</td></tr><tr><td><a data-footnote-ref href="#user-content-fn-4">HEIC</a></td><td>image/heic</td><td>heic</td><td></td></tr><tr><td><a data-footnote-ref href="#user-content-fn-5">HEIF</a></td><td>image/heif</td><td>heif</td><td>Single HEVC-encoded image only.</td></tr></tbody></table>

### Zip Files

As a convenience for testing, it is possible to upload Zip files to the [Live Test](/models/live-test.md).

The API does not support sending Zip files.

### API File Limits

These limits apply to all files sent to the API, regardless of type.

<table><thead><tr><th width="170.800048828125">Limit type</th><th width="152.7999267578125">All Paid Plans</th><th width="162.4000244140625">Free Trial</th></tr></thead><tbody><tr><td>File Size</td><td>100 MB</td><td>100 MB</td></tr><tr><td>Number of Pages</td><td>No limit</td><td>10 pages</td></tr></tbody></table>

If you have access to the file locally, there are workarounds available for these limits:

* [Load and Adjust a File](/integrations/client-libraries-sdk/load-and-adjust-a-file.md#manipulate-pdf-pages)
* [Load and Adjust a File](/integrations/client-libraries-sdk/load-and-adjust-a-file.md#compress-files)

Requires using our [Client Libraries / SDKs](/integrations/client-libraries-sdk.md).

### Live Test File Limits

These limits apply to files sent to the [Live Test](/models/live-test.md).

<table><thead><tr><th width="170.800048828125">Limit Type</th><th width="152.7999267578125">All Paid Plans</th><th width="162.4000244140625">Free Trial</th></tr></thead><tbody><tr><td>Document File Size</td><td>50 MB</td><td>50 MB</td></tr><tr><td>Number of Pages</td><td>50 pages</td><td>10 pages</td></tr><tr><td>Zip File Size</td><td>100 MB</td><td>100 MB</td></tr></tbody></table>

## Accepted URLs

It is possible to send an URL rather than binary data to the API.

An URL pointing to all [accepted files](/integrations/technical-limitations.md#accepted-files) may be used, if it adheres to the [API file limits](/integrations/technical-limitations.md#api-file-limits).

In addition, the source URL must adhere to the following rules:

* Secured using TLS (HTTPS).
* Publicly available using only the URL, no authentication *headers*.
* Authentication may be provided in the URL as query parameters: username+password or token.\
  For example, Amazon S3 signed URLs will work.
* Contents must be a binary file (raw bytes, **not** base64-encoded).
* File contents cannot be encrypted.
* The Mindee server will **not** follow redirections (HTTP 3xx).

Sending an URL to the Live Test is not supported.

## Rate Limits

Burst calls to the Mindee API are limited to ensure the stability of the platform for all users.

These rate limits apply to an entire organization, meaning the combination of all models, origin IPs, and API keys.

The following limits are enforced:

<table><thead><tr><th width="254">Limit Type</th><th>Limit Value</th></tr></thead><tbody><tr><td>Send for Processing (POST)</td><td>200 requests per minute</td></tr><tr><td>Polling (GET)</td><td>1200 requests per minute<br><em>Normally, this is handled by the client library.</em></td></tr></tbody></table>

If rate limits are exceeded, the server will return a HTTP 429 error.

However, there are no limits to the **total number of files** sent, so long as they adhere to the rate limits.

{% hint style="success" %}
Enterprise users: if you have needs beyond these limits, get in touch with the [sales team](mailto:hello@mindee.com) for a custom solution.
{% endhint %}

## Data Schema

### Number of Fields in the Data Schema

The recommended maximum number of fields is 25 for a Data Schema.

While there will be no errors, beyond this number response times will increase.

### Names of Fields

The field *name* must only contain:

* lowercase Latin letters without accents (a-z)
* numbers (0-9)
* underscores (`_`), but neither first nor last characters can be an underscore.
* the following names cannot be used: `value`, `fields`, `items`.

## Webhooks

Webhook URLs must adhere to the the following rules:

* Secured using TLS (HTTPS).
* Publicly available using only the URL, no authentication *headers*.
* Authentication may be provided in the URL as query parameters: username+password or token
* The Mindee server will **not** follow redirections (HTTP 3xx).
* The route should return OK (HTTP 2xx) when successful.

[^1]: Joint Photographic Experts Group

[^2]: Portable Network Graphics

[^3]: Tag Image File Format

[^4]: High-Efficiency Image Container

[^5]:


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mindee.com/integrations/technical-limitations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.