BlueForge Docs

forge api-key

Manage project API keys.

Command

forge api-key <subcommand> [args]

Arguments

None. Use a

<subcommand>
— run
forge --help
for per-subcommand arguments.

Subcommands

SubcommandUsage
create
forge api-key create --project <slug> --name <key-name>
list
forge api-key list --project <slug>
delete
forge api-key delete <key-id>

Flags per subcommand

create:

FlagTypeRequiredNotes
--project
stringyesProject slug
--name
stringyesKey display name

list:

FlagTypeRequiredNotes
--project
stringyesProject slug

Examples

Create a key:

forge api-key create --project my-app --name ci-key
# → Key: bf_key_xxxxx  (shown once only)

List keys:

forge api-key list --project my-app
# → bf_key_xxx  ci-key      active   2026-07-01
# → bf_key_yyy  dev-key     active   2026-06-15

Delete a key:

forge api-key delete bf_key_xxxxx --yes

Errors

Exit codeMeaning
0Success
1Missing required arguments
2Auth failure

Pitfalls

  • Plaintext shown once
    create
    prints the plaintext API key exactly once. Save it immediately.
  • List hides secrets
    list
    never returns plaintext key values, only metadata.

See also

{auto-injected}

Tested against

{auto-injected}