Read scan status and counts. A scan belongs to the requesting user and can expire. The service rechecks current permissions and saved conversation access before returning it; permission changes can block access.
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.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
The request is unauthorized.
Access denied by credential scopes, role or FLEXI exclusion, workspace permissions, or billing-related restrictions. Dunning can return JSON with an error field; other denials may have no JSON body.
Too many requests. Either the rate limit has been exceeded or usage limits have been reached.