First install & authentication can result in an `API Error 404: Not Found`

TL;DR

Install the latest Axiom CLI. The breakage came from a client-library/API compatibility mismatch, and the maintainer shipped a corrected release.

Steps

1. Install the latest Axiom CLI. The breakage came from a client-library/API compatibility mismatch, and the maintainer shipped a corrected release. Users confirmed the fixed CLI works again, so updating is the whole fix.
2. Source: https://github.com/axiomhq/cli/issues/230 (Axiom)

When to use

Use this skill when you run into "First install & authentication can result in an API Error 404: Not Found".

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

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/axiomhq/cli/issues/230

In gh:axiomhq/cli#230, the issue was: ### What happened I just installed the cli and followed the basic initial steps to get going: - install cli with ❯ go install github.com/axiomhq/cli/cmd/axiom@latest - auth with ❯ axiom auth login - successful browser auth w/ my github account The moment the oauth callback returned to your host the CLI returned gave me a 404. Screenshot shows full context.. The verified answer: Install the latest Axiom CLI. The breakage came from a client-library/API compatibility mismatch, and the maintainer shipped a corrected release. Users confirmed the fixed CLI works again, so updating is the whole fix.. Issue URL: https://github.com/axiomhq/cli/issues/230