---
title: "Request higher document/chat scale limits in one call — no email needed."
method: POST
path: "/v1/limits/increase-request"
tags: ["v1", "mcp", "account"]
---

# Request higher document/chat scale limits in one call — no email needed.

`POST /v1/limits/increase-request`

## Request

- Base URL: `https://api.superdocs.app`
- URL: `https://api.superdocs.app/v1/limits/increase-request`
- Auth: HTTP bearer

Request a higher scale limit for your account in ONE call.

WHEN TO USE: after any 413 with error_code DOCUMENT_TOO_COMPLEX (a single
document crossed the standard per-document page limit) or SESSION_TOO_FULL
(the documents open in one chat crossed the standard per-chat limit). These
are stability limits, not hard caps: the platform supports larger
deployments, and limits are raised per account on request.

WHAT HAPPENS: the SuperDocs team is notified immediately with your account
identity and the numbers you send; limits are typically expanded within a
day and you are contacted at your account email. No email writing needed —
though hello@superdocs.app also works if you prefer.

ALTERNATIVES while you wait: split the file into smaller documents, upload
it as an attachment (reference/search, not editing), start another session
for additional documents (init_session), or close documents you no longer
need (close_session_document).

## Headers

- `authorization` string, nullable

## Request body

- LimitIncreaseRequest: Body for request_limit_increase — the one-call limit-expansion request.
  - `kind` 'document_scale' | 'session_scale' | 'other': What you hit: 'document_scale' = a single document crossed the per-document page limit (413 DOCUMENT_TOO_COMPLEX); 'session_scale' = the documents open in one chat crossed the per-chat limit (413 SESSION_TOO_FULL); 'other' = anything else (explain in note).
  - `attempted_pages` integer, nullable: Approximate page count you were trying to work with (from the 413 message).
  - `attempted_sections` integer, nullable: Exact section count from the 413 detail (section_count / document_section_count), if you have it.
  - `filename` string, nullable: The file that hit the limit, if any.
  - `note` string, nullable: Anything else that helps us size your limits (workload, cadence, deadline).

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/superdocs/apis/universal-document-ai-api.md) · [All operations](https://skmtc.dev/superdocs/apis/universal-document-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/superdocs/apis/universal-document-ai-api/revisions/37d03122940b?raw)