One change
List chats
api/compliance/apps/chats/list
Nearest release: v2.1.242, published an hour before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
api/compliance/apps/chats/list Changed · +17 / -8 lines
from line 11
compliance review. Results are sorted chronologically (time ascending) by the `order_by` key, with ties broken by id. +**Deprecation notice:** Combining `user_ids[]` with any `updated_at.*` +filter is deprecated and will be rejected with HTTP 400 after +2026-09-22. For incremental polling by update time, omit `user_ids[]` +and set `order_by=updated_at` with `after_id` cursor pagination — +this returns the same chats across the whole organization in a single +request stream. For per-user listing, use `created_at.*` filters (or +no time filter) with the default `order_by`. `user_ids[]` with +`order_by=updated_at` is already rejected. + ### Query Parameters - `after_id: optional string`
from line 72
- `gt: optional string` - Filter chats updated after this time (RFC 3339 format) + Filter chats updated after this time (RFC 3339 format). Combining updated_at filters with `user_ids[]` is deprecated and will be rejected after 2026-09-22; for updated_at-windowed polling, omit `user_ids[]` and use `order_by=updated_at` with `after_id` pagination. - `gte: optional string` - Filter chats updated at or after this time (RFC 3339 format) + Filter chats updated at or after this time (RFC 3339 format). Combining updated_at filters with `user_ids[]` is deprecated and will be rejected after 2026-09-22; for updated_at-windowed polling, omit `user_ids[]` and use `order_by=updated_at` with `after_id` pagination. - `lt: optional string` - Filter chats updated before this time (RFC 3339 format) + Filter chats updated before this time (RFC 3339 format). Combining updated_at filters with `user_ids[]` is deprecated and will be rejected after 2026-09-22; for updated_at-windowed polling, omit `user_ids[]` and use `order_by=updated_at` with `after_id` pagination. - `lte: optional string` - Filter chats updated at or before this time (RFC 3339 format) + Filter chats updated at or before this time (RFC 3339 format). Combining updated_at filters with `user_ids[]` is deprecated and will be rejected after 2026-09-22; for updated_at-windowed polling, omit `user_ids[]` and use `order_by=updated_at` with `after_id` pagination. - `user_ids: optional array of string` - Filter to chats created by specific users (max 10 per request). Omit for an org-wide query. Enumerate IDs via `GET /v1/compliance/organizations/{org_uuid}/users`. + Filter to chats created by specific users (max 10 per request). Omit for an org-wide query. Enumerate IDs via `GET /v1/compliance/organizations/{org_uuid}/users`. Deprecated combination: passing `user_ids[]` together with any `updated_at.*` filter is deprecated and will be rejected after 2026-09-22. For `updated_at`-windowed polling, omit `user_ids[]` and use `order_by=updated_at` with `after_id` pagination. ### Header Parameters
from line 118
- `model: string or null` - Model selected for this chat (e.g. 'claude-opus-4-7'). May be null for legacy chats that never had a model recorded. + Model selected for this chat (e.g. 'claude-opus-5'). May be null for legacy chats that never had a model recorded. - `name: string`
from line 182
"created_at": "2025-06-07T08:09:10Z", "updated_at": "2025-06-07T09:10:11Z", "organization_id": "org_abc123", - "organization_uuid": "abcdef0123-4567-89ab-cdef-0123456789ab", + "organization_uuid": "abcdef01-2345-6789-abcd-ef0123456789", "project_id": "claude_proj_xyz789", - "model": "claude-opus-4-7", + "model": "claude-opus-5", "user": { "id": "user_xyz456", "email_address": "[email protected]"