Skip to content
CHAMPREPCHAMPREPCHAMPREP Docs

CHAMPREP CLI overview

The CHAMPREP CLI is the terminal interface to supported CHAMPREP services. It is a local static binary, but every networked command goes through the public API Gateway so the same account, service access, scopes, quotas, and audit controls continue to apply.

Supported workflows

Section titled “Supported workflows”

The current CLI includes command families for:

  • authentication, profile selection, and your account, plan, and usage;
  • Drive files, folders, transfers, and storage usage;
  • Mail messages, threads, accounts, and domains;
  • Chat rooms and messages;
  • Contacts;
  • Learn courses and enrollments;
  • Notes;
  • CHAMPREP AI conversations and usage;
  • Meet rooms;
  • Calendar events;
  • Work boards and tickets;
  • Invoices (list, read, issue, send);
  • Forms and responses;
  • the organization chart and people search;
  • Business (organization) info, members, and usage;
  • API-key management, webhook subscriptions, and read-only billing;
  • local configuration, shell completion, and version information.

Run champrep --help for the command tree shipped by the installed binary. That output is authoritative for its version.

Three-step journey

Section titled “Three-step journey”
  1. Install the CLI.
  2. Authenticate securely.
  3. Run a supported command.
Terminal window
champrep auth login
champrep auth whoami
champrep drive quota
champrep calendar today

Gateway-only network model

Section titled “Gateway-only network model”

The CLI does not call Drive, Mail, Calendar, AI, or another service backend directly. It uses the Gateway selected for the active environment. Do not point CHAMPREP_API_URL at an individual service API; that variable is intended only for a Gateway-compatible development or smoke-test endpoint.

Interactive and automated authentication

Section titled “Interactive and automated authentication”
  • Use champrep auth login for a person at a terminal. It opens a browser approval flow and stores the resulting credential in the operating-system keychain.
  • Use champrep auth token to store a scoped API key for longer-lived automation.
  • Use the CHAMPREP_TOKEN environment variable for ephemeral CI jobs where a secret manager injects the key at runtime.

See CLI authentication and API keys for automation before using a credential in a script.

Next steps

Section titled “Next steps”