Documentation menu

Limits

Sess rejects anything over a limit with an explicit error; it never truncates or guesses. Limit changes apply prospectively and are announced in the changelog.

On this page

Requests and content

Request and content limits
WhatLimitError
Request body256 KiB413 PAYLOAD_TOO_LARGE
Page content (UTF-8 bytes of the canonical Surface)128 KiB413 PAYLOAD_TOO_LARGE
Title1 to 200 characters, not only spaces400 INVALID_SCHEMA
DescriptionUp to 4,000 characters400 INVALID_SCHEMA
Display Sessions: dataAt least one top-level key; each value a string, number, boolean or null, a record of such values, or a table of 1 to 100 such records with the same keys400 INVALID_SCHEMA
Human link lifetime: Sessions created with your API key7 days after the Session is created (developer account, free workspace) Draft — lands with P1 increment 2Generic "not found" page
Session content kept: Sessions created with your API key7 days after the Session is completed or its link expires, whichever comes first (developer account, free workspace) Draft — lands with P1 increment 2. See Retention.404 SESSION_NOT_FOUND
Human link lifetime: the operator key only (held by the Sess team, never issued to developers)30 days after the Session is createdGeneric "not found" page
Session content kept: the operator key only30 days after the Session is completed or its link expires, whichever comes first404 SESSION_NOT_FOUND

Files, images, external media and remote content are not supported. The exact schemas are in the API reference.

Interactive Sessions

Interactive Surface limits, per revision
WhatLimit
Components (heading, text, record, field)1 to 100
Input fieldsUp to 50
Actions1 to 5
Choices in one list (enum values)Up to 100
Key/value pairs in one recordUp to 50
Text componentUp to 4,000 characters
Text fieldUp to 4,000 characters unless the field declares maxLength (at most 10,000)
Accepted responsesOne per revision

Unsupported components fail with 400 UNKNOWN_COMPONENT; unsupported schema keywords with 400 INVALID_SCHEMA.

A cap on accepted rounds per Session (initially 10). Draft — lands with P1 increment 2

Webhooks

Webhook limits
WhatLimit
EndpointsOne per workspace: an https:// URL on port 443, up to 2,048 characters, no user info or fragment, resolving to a public address
VerificationValid for 30 days; verify again to renew
Each attempt10-second timeout, no redirects followed, your response read up to 64 KiB
RetriesUp to 12 attempts within 24 hours; Retry-After honored up to 1 hour
Secret rotationThe previous secret keeps signing for 24 hours

No-signup trial

Trial limits
WhatLimit
New trials3 per client per rolling 24 hours, and 200 overall per rolling 24 hours
Sessions in one trialUp to 3 active at a time, and 10 created within the trial's 24-hour creation window
Answer window1 hour after the Session is created
Result retrieval24 hours after the answer window ends
RoundsOne answered revision per trial Session (publishing a next revision needs an API key)
Webhooks and outbound callsNone

A "client" is identified by the network address the request comes from. People who share a network, such as an office, a VPN or a mobile carrier, may share the per-client allowance and see 429 RATE_LIMITED before they have started three trials themselves. The response carries a Retry-After header. These are preview settings and may be tightened if abused, without changing Sessions already created.

Plan limits

Draft — lands with P1 increment 2 Planned; not available on the current API.

Plan limits
PlanActive SessionsVolumeLive lifetimeWebhooks
Free workspace25 (planned)500 resolved Sessions per month (planned)Up to 7 daysYes, verified endpoints
Paid pilot (planned)1005,000 resolved Sessions per monthUp to 30 daysYes, verified endpoints

Every developer workspace is on the free workspace today. Its 7-day live lifetime and its retention (see Retention) are enforced for each Session; the active-Session cap and the monthly volume are planned and not yet enforced. The paid pilot is not available yet.

Once allowances are enforced, a new Session beyond an allowance is rejected with a clear error. Work already in progress, including accepted responses and their delivery, still finishes. Sess never charges an automatic overage.