HSX_E_API_NOT_FOUND
API resource not found.
What this error means
404 from the upstream API.
When this error stops a command, hs-x exits with code 50. With --json, the failure is reported as a structured error whose code field is HSX_E_API_NOT_FOUND — stable to match on in scripts and agents.
Likely causes
- Typo in the path
- Resource doesn't exist
- Resource not shared with your PAK
How to fix it
- Double-check the path
- Re-run with
--debugto see the wire request
Still stuck? Re-run the command with --debug for the wire-level detail, or hs-x doctor to check accounts, link state, and connectivity in one pass.
Keep going