Understanding KAKR error messages

Whenever a request doesn't do what you expected, check these in order:

1. The successful field, not just the HTTP status — a logical failure can still be HTTP 200. See understanding the API response envelope.
2. The message field — this is where the explanation lives when successful is false.
3. Whether it's a known pattern — check the API error code reference and common API errors before assuming it's novel.
4. Authentication-specific messages like "challenge expired" or "invalid signature" have their own dedicated article: challenge expired or invalid signature.

If none of that explains it, submit a ticket with the full response body — see safe diagnostic information without sharing secrets for what's safe to include.