CLIauth
capxul auth verify
finish signing in (scripts and agents)
Runs in: devnet · staging · production · Moves money: no
Usage
capxul auth verify [flags] [<code>]Arguments
| Argument | Type | Required | Description |
|---|---|---|---|
<code> | string | no | The six-digit code from your email (or use --otp-stdin) |
Flags
| Flag | Type | Required | Description |
|---|---|---|---|
--email | string | no | Email address |
--otp-stdin | boolean | no | Read the six-digit OTP from standard input; never pass it as an argument |
Every command also takes the global flags.
Examples
# Finish the sign-in auth login started
$ capxul auth verify 123456Returns
The data of the result that --json prints:
{ authenticated, credentialKind, email, authUserId, expiresAt, profile, smartAccount, lifecycle, setupState: 'ready' | 'setup-required' }; setup-required adds { status: 'awaiting_setup', setupUrl, next: { argv } }. It never opens a browser, and journeyIdErrors
Generated from capxul schema auth verify.