nxtkeys CLI

Command-line client for managing nxtkeys orgs, projects, and secrets via the API.

Prerequisites

• Node.js 18+
• Verified account in https://nxtkeys.com

Installation

To install the CLI globally, use the following command:

npm install -g nxtkeys

Usage

After installation, you can use the nxtkeys command directly in your terminal. For example:

nxtkeys login

Refer to the commands listed below for more details.

Auth

• nxtkeys login – prompts for email/password and stores the token in your OS keychain.
• nxtkeys logout – removes the stored token.
• nxtkeys whoami – shows the current authenticated user.

Organization commands

• nxtkeys org list – list orgs you belong to (shows role, marks current).
• nxtkeys org create <name> – create an organization.
• nxtkeys org delete <orgId> – delete an organization.
• nxtkeys org switch <orgId> – set current org context (also clears project context).

Project commands

• nxtkeys project list [--organization_id <orgId>] – list projects (optionally filter by org; defaults to orgs you’re a member of).
• nxtkeys project create <name> – create a project in the current org context.
• nxtkeys project delete <projectId> – delete a project.
• nxtkeys project switch <projectId> – set current project (also updates org context to the project’s org).

Secret commands

• nxtkeys secret list [--project <projectId>] – list secrets for the project (uses current project if omitted).
• nxtkeys secret set <KEY=VALUE> [--project <projectId>] – create or update a secret key.
• nxtkeys secret delete <key> [--project <projectId>] – delete a secret by key.
• nxtkeys secret export <path> [--project <projectId>] [--format env|json] – export secrets to a file.
• nxtkeys secret import <path> [--project <projectId>] – import secrets from env/json file; upserts per key.

Sync helpers

• nxtkeys pull [--project <projectId>] – pull secrets to .env in the current directory.
• nxtkeys push --project <projectId> – push secrets from .env (uppercases keys; best used after project switch).

Secrets behavior

• Keys are case-sensitive in the API; some commands uppercase keys on create to keep consistency.
• Current org/project context is stored in the CLI config and used when flags are omitted.