Query current conversations within a time range by last customer message time. Results can be limited by the active channel scope; a channel filter does not guarantee complete coverage across all connected channels. With page.size, return a synchronous page (200); without it, create or reuse a durable scan (202). count_only is asynchronous. Query predicates honor current conversation access control. Scan results can reflect state evaluated over time; an accepted scan is not a completed result. The service can reject invalid fields, stale cursors, unavailable evidence, or an idempotency-key conflict. Some query validation and scan-state failures currently return HTTP 500. Inspect the actual status and response body; do not assume every invalid query returns 400 or retry an unchanged request indefinitely.

Permissions

For API access tokens and OIDC tokens, satisfy at least one of: api, conversationsv3:read, wati_integration:read. API access tokens may satisfy a listed scope through the configured scope hierarchy; OIDC tokens are checked against their scope claims. Legacy JWT authentication does not use this scope check. Authentication, role, tenant, and applicable feature or plan checks still apply. For HTTP 403, check the credential type, applicable scopes, roles, and workspace access; 403 does not always mean a missing scope. Authentication/authorization failures do not guarantee a JSON response body. Allowed roles: DEVELOPER, TRIAL, ADMINISTRATOR, EXTERNAL_ADMINISTRATOR, PARTNER_ADMINISTRATOR, AI_OPERATOR, or API_TOKEN. A user with FLEXI_TRIAL or FLEXI_PAID is explicitly denied, even if another listed role is present. A qualifying outstanding invoice can also result in a 403 response.