inbox-api-cli 0.1.0

mail-cli — .NET CLI Tool

Command-line tool for interacting with the Inbox API. Provides email account management, message operations, sending, search, and draft management. Authenticates via API tokens (cw_ prefix).

Prerequisites

• .NET 9 SDK
• A running Inbox API instance
• An API token (generated from the web UI or API)

Install / Run

# Run directly (from backend/ directory)
dotnet run --project mail-cli -- [command] [options]

# Build a self-contained single-file executable
dotnet publish mail-cli -c Release

# The published binary is at mail-cli/bin/Release/net9.0/{runtime}/publish/mail-cli

Configuration

Configure the CLI with the configure command:

# Interactive configuration
dotnet run --project mail-cli -- configure

# Or use environment variables
export INBOX_API_URL=http://localhost:5015
export INBOX_API_TOKEN=cw_your_api_token_here

Configuration is stored in a local config file managed by ConfigService.

Commands

Global Options

Examples

# List email accounts
dotnet run --project mail-cli -- accounts list

# Send an email
dotnet run --project mail-cli -- send --to user@example.com --subject "Hello" --body "Message"

# Search messages
dotnet run --project mail-cli -- search --query "invoice" --json

# List messages in JSON format
dotnet run --project mail-cli -- messages list --json

Structure

mail-cli/
├── Program.cs          # Entry point, command registration, error handling
├── Commands/           # Command handlers (11 files)
│   ├── AccountCommands.cs
│   ├── MessageCommands.cs
│   ├── SendCommand.cs
│   ├── ReplyCommand.cs
│   ├── DraftCommands.cs
│   ├── FolderCommands.cs
│   ├── SearchCommand.cs
│   ├── TokenCommands.cs
│   ├── ConfigureCommand.cs
│   ├── CommandHelper.cs
│   └── GlobalOptions.cs
├── Models/
│   ├── ApiModels.cs    # API response types
│   └── ConfigModels.cs # Local configuration types
└── Services/
    ├── ApiClient.cs    # HTTP client wrapper
    ├── ConfigService.cs # Config file management
    └── OutputService.cs # Console output formatting (Spectre.Console)

Key Dependencies

Notes

• This is a standalone project — it does not reference saas-api or saas-data
• All API communication is over HTTP via ApiClient
• The binary can be published as a self-contained single-file executable (PublishSingleFile + SelfContained are enabled in the csproj)
• Error handling maps API errors to user-friendly messages with appropriate exit codes (0=success, 1=error, 2=auth failure, 3=connection failure)