Skip to main content
POST
Request higher document/chat scale limits in one call — no email needed.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

authorization
string | null

Body

application/json

Body for request_limit_increase — the one-call limit-expansion request.

kind
enum<string>
default:document_scale

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).

Available options:
document_scale,
session_scale,
other
attempted_pages
integer | null

Approximate page count you were trying to work with (from the 413 message).

Required range: 0 <= x <= 10000000
attempted_sections
integer | null

Exact section count from the 413 detail (section_count / document_section_count), if you have it.

Required range: 0 <= x <= 10000000
filename
string | null

The file that hit the limit, if any.

Maximum string length: 255
note
string | null

Anything else that helps us size your limits (workload, cadence, deadline).

Maximum string length: 2000

Response

Successful Response