> ## Documentation Index
> Fetch the complete documentation index at: https://developers.telnyx.com/llms.txt
> Use this file to discover all available pages before exploring further.

# KV CLI

> Manage Telnyx KV namespaces and keys from your terminal using the telnyx-edge CLI, including create, list, put, get, and delete operations.

Manage KV namespaces and keys using the `telnyx-edge` CLI.

## Namespace Management

```bash theme={null}
# List all namespaces
telnyx-edge storage kv list

# Create a namespace (name: lowercase letters, numbers, hyphens)
telnyx-edge storage kv create --name my-cache

# Get a namespace
telnyx-edge storage kv get <namespace-id>

# Delete a namespace
telnyx-edge storage kv delete <namespace-id>
```

## Key Operations

The value is stored verbatim — pass it as a positional argument, or use `--path` to store the contents of a file.

```bash theme={null}
# List keys in a namespace
telnyx-edge storage kv key list <namespace-id>

# List keys filtered by prefix
telnyx-edge storage kv key list <namespace-id> --prefix user/

# Get a value (prints the raw stored bytes)
telnyx-edge storage kv key get <namespace-id> user/123

# Put a value
telnyx-edge storage kv key put <namespace-id> user/123 "hello"

# Put a value from a file
telnyx-edge storage kv key put <namespace-id> user/123 --path ./value.json

# Delete a key
telnyx-edge storage kv key delete <namespace-id> user/123
```

### Key list flags

| Flag       | Description                                                   |
| ---------- | ------------------------------------------------------------- |
| `--prefix` | Filter keys by prefix                                         |
| `--cursor` | Pagination cursor from a previous response                    |
| `--limit`  | Maximum number of keys to return, `1`–`1000` (default `1000`) |

<Note>
  Keys may contain `a-z`, `A-Z`, `0-9`, and `-` `_` `/` `=` `.` (no colons). KV has no native TTL or metadata; there are no `--ttl` or `--metadata` flags. See [Key expiration](/docs/edge-compute/kv/ttl-and-metadata) for an application-level expiry pattern.
</Note>