Description
After upgrading from v0.3.1 to v0.4.0, basecamp me returns a 404 error:
{
"ok": false,
"error": "authorization request failed: {\"status\":404,\"error\":\"Not Found\"}",
"code": "api_error"
}Exit code 7.
Environment
- CLI version: 0.4.0
- Platform: Linux aarch64 (Debian bookworm)
- Auth: OAuth token via
BASECAMP_TOKEN env var
basecamp doctor: 8 passed, 1 warning (no global config), 1 skipped (shell completion)- Account access: confirmed working
Steps to Reproduce
- Upgrade from v0.3.1 to v0.4.0
- Run
basecamp me --account <id> --json
- Also fails without
--account and without --json
Notes
basecamp auth status reports authenticatedbasecamp doctor shows API connectivity and account access both pass- All other commands work fine (
projects list, message, recordings trash, etc.)
- Token was refreshed after upgrade, same result
Likely a scope or endpoint change in v0.4.0 that affects the me / authorization endpoint.
Description
After upgrading from v0.3.1 to v0.4.0,
basecamp mereturns a 404 error:{ "ok": false, "error": "authorization request failed: {\"status\":404,\"error\":\"Not Found\"}", "code": "api_error" }Exit code 7.
Environment
BASECAMP_TOKENenv varbasecamp doctor: 8 passed, 1 warning (no global config), 1 skipped (shell completion)Steps to Reproduce
basecamp me --account <id> --json--accountand without--jsonNotes
basecamp auth statusreports authenticatedbasecamp doctorshows API connectivity and account access both passprojects list,message,recordings trash, etc.)Likely a scope or endpoint change in v0.4.0 that affects the me / authorization endpoint.