List text conversations needing attention
The analysed text conversations a person should read first: those with a sentiment score or a
failure outcome, created in the window, ordered by sentiment ascending (most negative first),
then newest first. Threads that failed but carry no score sort after every scored one. Open a
row with GET /api/conversations/{conversationId} using the returned id.
No data. An empty data array when nothing qualifies. Unanalysed threads never appear here.
Idempotency. Read-only; safe to retry.
Consistency. Computed live; Cache-Control: private, max-age=30, stale-while-revalidate=900.
Access
- Required scope:
read. Signed-in users need the owner, admin, member or viewer role. - Rate limit: Analytics — 30 requests/min per workspace, shared with the rest of
/api/analytics/*; also counts against the general API limit. See Rate limits. - Plan: Available on every plan. Requires an active subscription (
active,trialingorpast_due); without one the request is refused with403 BILLING_ERROR(metadata.kind: subscription_required).
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Query parameters
Window in days ending now. Integer 1-365; anything else is rejected with 400.
Maximum rows to return. Never rejected: values above 50 are clamped to 50, negative values to 1,
and 0 or a non-numeric value becomes 10. Pass an integer.

