# Common API Error Codes

<table><thead><tr><th width="89">Code</th><th width="201.7999267578125">Error</th><th>When it happens</th></tr></thead><tbody><tr><td>400</td><td>Bad request</td><td>Request data is invalid or doesn’t match the API docs. The response can include a detailed issue description.</td></tr><tr><td>401</td><td>Unauthorized</td><td>Auth token is invalid, incorrect, or expired.</td></tr><tr><td>402</td><td>Payment Required</td><td>Billing denies functionality due to missing payment or plan restrictions.</td></tr><tr><td>403</td><td>Forbidden</td><td>The caller doesn’t have access or permissions for the requested entity. The response can include a detailed issue description.</td></tr><tr><td>404</td><td>Not found</td><td>The requested entity doesn’t exist or was deleted (hard delete).</td></tr><tr><td>409</td><td>Conflict</td><td>Rare. Appears when two entities conflict. Usually retried, so users don’t see it.</td></tr><tr><td>410</td><td>Entity gone</td><td>The requested entity was deleted (soft delete). Example: a template was deleted while being processed.</td></tr><tr><td>422</td><td>Unprocessable entity</td><td>The requested entity can’t be processed. Example: approve/reject the same envelope twice.</td></tr><tr><td>425</td><td>Too early</td><td>The request was sent too early. Example: the endpoint enforces a minimum time period between requests.</td></tr><tr><td>429</td><td>Too many requests</td><td>Too many requests were sent to the endpoint and you exceeded the rate limits.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://support.docstudio.com/docstudio-docs/docstudio-for-developers/api-documentation/common-api-error-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.