version
version prints the cli's own package version alongside the server's current API date and compatibility catalog. acts on the cli's own state — no site / machine targeting, no auth required (the endpoint is unauthenticated; the cli forwards a token if one is configured but does not require it). tier: [ready].
use this to:
- confirm the cli + server are on compatible api versions before running a long script
- inspect the server's current API date and the supported date catalog
version
owlette version [--json]| flag | type | required | description |
|---|---|---|---|
--json | boolean (global) | no | emit the structured record instead of the one-line human form |
examples
# default — one-line summary
owlette version
# cli 1.4.0 | server 2026-04-15 | supported versions: 2026-01-10, 2026-02-28, 2026-04-15# json envelope — script-friendly
owlette version --json
# {
# "cli": "1.4.0",
# "server": "2026-04-15",
# "supportedVersions": ["2026-01-10", "2026-02-28", "2026-04-15"],
# "minimumVersion": "2026-01-10"
# }backing: GET /api/version. unauthenticated — token is forwarded as Authorization: Bearer <token> if one is configured, but the endpoint does not require it.
output
human mode
a single line on stdout:
cli <X.Y.Z> | server <YYYY-MM-DD> | supported versions: <D1>, <D2>, ...json mode (--json)
{
"cli": "1.4.0",
"server": "2026-04-15",
"supportedVersions": ["2026-01-10", "2026-02-28", "2026-04-15"],
"minimumVersion": "2026-01-10"
}| field | type | meaning |
|---|---|---|
cli | string | the cli's own package.json version (resolved by walking up from the binary to the nearest @owlette/cli package), or "unknown" if it can't be located |
server | string | the server's current API date (current from the response) |
supportedVersions | string[] | every supported API date returned by the api, in server order |
minimumVersion | string | lex-min of supportedVersions (lex order on YYYY-MM-DD is chronological), or server if the list is empty |
note:
versionpredates the{ ok, data }wrapper. its json envelope is the raw shape above for compatibility with scripts written against earlier cli versions — see overview.
exit codes
0— success1— network failure, non-2xx response fromGET /api/version, or unexpected response shape (missingcurrentor emptysupported)
notes
- scope: user (acts on the cli's own state — no site / machine targeting)
- tier:
[ready] - auth: not required. the
/api/versionendpoint is public. if a token is configured for the active profile the cli forwards it, but a missing / invalid token does not cause the command to fail - date ordering: the catalog uses dated
YYYY-MM-DDstrings, not semver. lex order on these strings == chronological order, which is how the cli computesminimumVersionfromsupportedVersions - related: overview for the cli's config story
user
owlette user manages platform users — promoting, demoting, granting site access, and soft-deleting accounts. superadmin token required on every verb. tier: ready — all seven verbs are wired to /api/users/* and covered by the public API contract.
webhook
CLI noun group planned. The public webhook API routes are live for developer preview, but no owlette webhook noun is registered in the current CLI. Full owlette webhook ... management commands remain planned; today the shipped top-level helpers are owlette listen and owlette trigger . See the readiness matrix for the route mapping.