Skip to main content

Documentation Index

Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

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

​
1. Log in

jetemail login
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: 
jetemail login --api-key api_xxxxxxxx --transactional-key transactional_xxxxxxxx
See Authentication for environment variables, profiles, and CI setups.

​
2. Send your first email

jetemail send --to you@example.com \
              --from noreply@yourdomain.com \
              --subject "Hello from jetemail"
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 --to alice@example.org \
              --from noreply@yourdomain.com \
              --subject "Welcome" \
              --html "<p>Hi <b>Alice</b></p>"
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

jetemail outbound domains list
In a terminal you get a compact table. In a pipe (| jq …, CI logs, AI agents) you get pretty JSON on stdout: 
jetemail outbound domains list | jq '.[] | .domain'

​
4. Run the self-test

jetemail doctor
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.