Skip to main content
You’ll need a JetEmail account and an api_… key from the dashboard.

​
1. Log in

login prompts for your api_… key, validates it against the API, and saves it to a local config file (chmod 600 on Unix). It also offers to save a transactional_… key if you plan to use email send. You can pass keys non-interactively:
See Authentication for environment variables, profiles, and CI setups.

​
2. Send your first email

If the body flags aren’t supplied, you’ll be prompted for the missing fields. Pass --html or --text to fill the body:
jetemail send is an alias for jetemail email send. See email for the full set of flags (CC/BCC, headers, attachments, scheduling, idempotency keys).

​
3. List a domain

In a terminal you get a compact table. In a pipe (| jq …, CI logs, AI agents) you get pretty JSON on stdout:

​
4. Run the self-test

Verifies your config file, API key, transactional key (if set), and that the API responds successfully.

​
Where to go next

Authentication

Environment variables, login flow, whoami, logout.

Output formats

--json, --raw, --quiet, terminal vs. pipe behaviour.

All commands

Full reference for every subcommand.

Live log tail

Watch mail move through the pipeline live.