---
title: "ezgh flags keys create"
description: "Create an SDK key; it's shown once."
---

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

# ezgh flags keys create

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh flags keys create --env <environment> --kind server|client --name <name> [flags]
```

Create an SDK key for an environment. The key is printed once, alone on stdout, and can't be shown again.

A server key (`--kind` server) is a secret for your backends: it reads every flag and its rules, and EZGH's server providers evaluate locally with it. A client key (`--kind` client) is publishable, for web pages: it sees only client-side flags, never their rules.

Part of [`ezgh flags keys`](/cli/reference/flags-keys).

## Examples

```sh
EZGH_FLAGS_SDK_KEY=$(ezgh flags keys create --env production --kind server --name checkout-api)
```

## Flags

| Flag | Type | Default | Description |
| --- | --- | --- | --- |
| `--env` | string |  | the environment's key (required) |
| `--kind` | string | `server` | server (secret, backends) or client (publishable, web pages) |
| `--name` | string |  | what uses the key (required) |

This command also takes the [global flags](/cli/reference#global-flags).

Source: https://docs.ezghcloud.com/cli/reference/flags-keys-create/index.mdx
