# namera session-key import

> Documentation index: [llms.txt](https://namera.ai/llms.txt).

Source: https://namera.ai/docs/cli/reference/session-keys/session-key-import

Import a dashboard-encrypted session key onto this machine.

Import a dashboard-encrypted session key onto this machine.

## Usage [#usage]

```sh
namera session-key import <encrypted-export> --host https://api.namera.ai
```

## Output [#output]

<div className="docs-response">

```text
Session key imported
  Status: imported
  Session Key ID: 0199dfe1-0000-7000-8000-000000000002
  Wallet ID: 0199dfe1-0000-7000-8000-000000000001
  Chains: eip155:84532
```

</div>

Example output uses fixture accounts and hashes, captured with the CLI's output
formatters. Plain-text output is shown without terminal colors; your values and
relative expiry dates will differ.

The command prompts for `Export passphrase` before printing this result. In JSON
mode it returns `status`, `sessionKeyId`, `walletId`, and `chains`:

<div className="docs-response">

```json
{
  "status": "imported",
  "sessionKeyId": "0199dfe1-0000-7000-8000-000000000002",
  "walletId": "0199dfe1-0000-7000-8000-000000000001",
  "chains": ["eip155:84532"]
}
```

</div>

## Arguments [#arguments]

### encrypted-export [#encrypted-export]

- **Type:** base64url string
- **Required:** yes

Copy the full encrypted export from the dashboard's import command. It is not
a private key or a file path. The export must match the expected API origin.
Enter its passphrase at the hidden prompt; there is no passphrase flag.

## Options [#options]

### --host [#--host]

- **Type:** absolute API URL
- **Default:** environment or profile origin

Use the host shown in the dashboard import command. Resolution order is
`--host`, `NAMERA_API_URL`, then the saved CLI profile. An unsaved `personal`
profile defaults to `https://api.namera.ai`; a new custom profile needs `--host`.

### --profile [#--profile]

- **Type:** `string`
- **Default:** `personal`

Used to find the expected API origin when neither `--host` nor
`NAMERA_API_URL` is provided. Import does not create a login profile.

The command also accepts [global options](https://namera.ai/docs/cli/reference/global-options):
`--output pretty|json`, `--quiet`, and `--help`.

## Storage and Recovery [#storage-and-recovery]

No API login is required. The CLI decrypts the export, then saves an encrypted
file protected by an independent OS-keyring secret. It never falls back to plaintext.

Import does not install the key onchain or grant access to a CLI/MCP connection.
Approve a network in the dashboard, then authorize the active key during login.
An already imported key is not overwritten.

If import fails, preserve your encrypted export. Check the passphrase, origin,
and OS-keyring access. On Linux, use persistent Secret Service; a memory-only
keyring cannot retain unlock secrets across reboots. Do not use `sudo` or
delete existing keys as a recovery shortcut.

## Errors [#errors]

Failures exit nonzero and are written to stderr. With `--output json`, inspect
`error.code` and `error.nextStep`. See [Output and Errors](https://namera.ai/docs/cli/output-and-errors).