curviate account checkpoint request

Re-request the challenge notification for a pending checkpoint (e.g. re-send an OTP email, SMS code, or mobile-app approval push). Not every challenge type supports it; an authenticator- app code has nothing to re-send. The response's resent boolean tells you honestly whether a new notification actually went out; the command still exits 0 either way. With --challenge it instead answers a challenge_selection checkpoint by picking the verification method.

Usage

curviate account checkpoint request <account-id> [flags]

Examples

curviate account checkpoint request acc_YOUR_ACCOUNT_ID
curviate account checkpoint request acc_YOUR_ACCOUNT_ID --challenge sms

Arguments

Argument	Required	Description
`account-id`	yes	The provisional account_id (acc_...) from the 202 checkpoint_required response.

Flags

Flag	Type	Required	Description
`--challenge`	string	no	Answer a challenge_selection checkpoint: an id from its challenges list (email \| sms \| whatsapp). Prints the next checkpoint and exits 12; solve it with `checkpoint solve`. Omit to re-send the current code.

Also accepts these global flags: --api-key, --profile, --account, --base-url, --timeout, --json, --fields, --preview, --verbose, --beta.

Exit codes: the exit code table. More commands: Account.