Skip to main content

​
Counting conversations

A session is counted on its first useful turn. Creating a session without calling /next does not consume a conversation. Later turns in the same session do not create another billable conversation. Your contract determines the allocation, possible overage, and rate limits. Check the Usage page in Zelinqa Studio for your organization’s current values.

​
Important technical limits

Every mutation requires Idempotency-Key; an existing-session mutation also requires state_version. Feedback metadata remains limited to 50 properties with simple values; see OpenAPI for each field’s exact bounds. These payload limits are separate from your plan’s usage and throughput limits.

​
Handling 429 responses

Use exponential backoff with jitter, respect any retry headers, and avoid synchronized bursts across workers.
Do not use retries to bypass a commercial quota or validation rule. Contact your administrator when a limit is persistently insufficient.