> 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/problem-database.md).

# Error Handling

Common error messages and their handling.

## Error Responses

All errors will contain the following information:

* Status: the HTTP status code.
* Title: a human-readable short description, it may not be unique.
* Detail: a human-readable description of the error, it will be unique.
* Code: a code to identify the specific error.\
  Provide this code when asking for support.

## 4xx Errors - Client Errors

<table><thead><tr><th width="130">HTTP Status</th><th>Possible Reasons</th></tr></thead><tbody><tr><td>400</td><td><ul><li>A required request parameter is missing.</li></ul></td></tr><tr><td>401</td><td><ul><li>Invalid API key. Make sure the key starts with <code>md_</code> and is <a href="/integrations/api-keys.md">active</a>.</li><li>Make sure you are calling the V2 API, your code should match <a href="/extraction-models/sdk-integration/quick-start.md">the samples</a>.</li><li>API keys are not JWTs: do not include <code>Bearer</code> in your <code>Authentication</code> header.</li></ul><p>Always prefer using the provided SDKs if possible.</p></td></tr><tr><td>402</td><td><ul><li>An optional feature is not in your plan.</li><li>Your subscription is either not active or exceeded limits.</li></ul></td></tr><tr><td>403</td><td><ul><li>You don't have access to the requested resource.</li></ul></td></tr><tr><td>404</td><td><ul><li>The requested resource does not exist.</li><li>The requested resource is not ready for use (usually a processing result).</li></ul></td></tr><tr><td>422</td><td><ul><li>Wrong format for a UUID.</li><li>Invalid or empty file sent.</li><li>Invalid parameter sent in a request.</li></ul></td></tr><tr><td>429</td><td><ul><li>Too many requests. Wait a few seconds and try again.<br>For more information, consult the section:  <a data-mention href="/integrations/technical-limitations.md#rate-limits">Technical Limitations</a>.</li></ul></td></tr></tbody></table>

## 5xx Errors - Server Errors

<table><thead><tr><th width="130">HTTP Status</th><th>Possible Reasons</th></tr></thead><tbody><tr><td>500</td><td><ul><li>Failed to run the inference.</li><li>Failed to process the request.</li></ul></td></tr></tbody></table>

### Mindee Status

Check to make sure that the API is fully operational.

You can also subscribe to be notified automatically.

<https://status.mindee.com/>


---

# 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/problem-database.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.