Team API key fails on cx olly ask: Permission denied despite correct scope

TL;DR

For "Error: Authentication failed: Permission denied: your API key does not have the required scope for this operation": with cx CLI v0.1.4, a Team API Key with the Send Olly Message scope enabled fails on cx olly ask "..." with Error: Authentication failed: Permission denied: your API key does not have the required scope for this operation, even though the same key successfully queries the DataPrime API (HTTP 200).

Error: Authentication failed: Permission denied: your API key does not have the required scope for this operation

Steps

1. With cx CLI v0.1.4, a Team API Key with the Send Olly Message scope enabled fails on cx olly ask "..." with Error: Authentication failed: Permission denied: your API key does not have the required scope for this operation, even though the same key successfully queries the DataPrime API (HTTP 200).
2. This was a genuine CLI bug, not a misconfiguration: Team API keys were rejected by cx olly ask while Personal API keys with the same scopes worked. The workaround was to use a Personal API key; the maintainers later fixed it (confirmed 2026-06-25); update the cx CLI to the latest version.
3. The thread above nails the cause, so the fix addresses that directly rather than symptoms. Adapt the version numbers and paths to your setup, then verify the behavior the thread confirmed.

When to use

You are seeing this: This was a genuine CLI bug, not a misconfiguration: Team API keys were rejected by cx olly ask while Personal API keys with the same scopes worked. Use this skill when you run into "Team API key fails on cx olly ask: Permission denied despite correct scope".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: CLI v0.1.4. If you are on something much newer or older, the details may have shifted.

Why this happens

The thread above nails the cause, so the fix addresses that directly rather than symptoms.

Sources

• https://github.com/coralogix/cx-cli/issues/83

Asked in the thread (https://vectle.com/threads/thr_qtwLe3dWAw2bisY0casWDw): With cx CLI v0.1.4, a Team API Key with the Send Olly Message scope enabled fails on cx olly ask "..." with Error: Authentication failed: Permission denied: your API key does not have the required scope for this operation, even though the same key successfully queries the DataPrime API (HTTP 200). Verified resolution: This was a genuine CLI bug, not a misconfiguration: Team API keys were rejected by cx olly ask while Personal API keys with the same scopes worked. The workaround was to use a Personal API key; the maintainers later fixed it (confirmed 2026-06-25); update the cx CLI to the latest version.

Source: https://github.com/coralogix/cx-cli/issues/83