Function AccountRecoveryBloksSubmitCode

AccountRecoveryBloksSubmitCode(
    input: AccountRecoveryBloksSubmitCodeInput,
): Effect<
    {
        logged_in_user: {
            full_name?: string
            | null;
            is_private?: boolean | null;
            is_verified?: boolean | null;
            pk: number;
            pk_id: string;
            profile_pic_url?: string | null;
            username: string;
        };
        status?: string;
        trusted_device_nonce?: string;
    },
    | BloksHttpError
    | LoginBloksParseError
    | AccountRecoveryBloksUnknownResponseError
    | AccountRecoveryBloksInvalidCodeError,
    | MobileSession
    | MobileDevice
    | BloksHttp
    | MobileApplication
    | SessionHeaderParser,
>
Submits the recovery code (code_entry_async). The wire shape is the recorded 451 submission: client_input_params in the recorded key order — the empty-string auth_secure_device_id, the aac (empty when the process has none), the code, the family/device ids and the session x-mid as machine_id; no vetted_device_nonces — and server_params echoed from the code-entry screen's "Continue" action in the recorded order.
Parameters
- input: AccountRecoveryBloksSubmitCodeInput
Returns Effect<
    {
        logged_in_user: {
            full_name?: string
            | null;
            is_private?: boolean | null;
            is_verified?: boolean | null;
            pk: number;
            pk_id: string;
            profile_pic_url?: string | null;
            username: string;
        };
        status?: string;
        trusted_device_nonce?: string;
    },
    | BloksHttpError
    | LoginBloksParseError
    | AccountRecoveryBloksUnknownResponseError
    | AccountRecoveryBloksInvalidCodeError,
    | MobileSession
    | MobileDevice
    | BloksHttp
    | MobileApplication
    | SessionHeaderParser,
>

Function AccountRecoveryBloksSubmitCode

Parameters

Settings