Pigeon is in early testing

Early testing means the dashboard, the HTTP API, and SMTP are open. Scale volumes above Pro are still written onto an account by hand. A domain can send only after its status says Verified.

What you can try this week

• A welcome or receipt from your own domain.
• A sending API key in one app, and a full-access key for domain setup.
• The audience, a broadcast, and an unsubscribe link on a template.
• The free plan: 3,000 emails in a UTC month, 100 in a UTC day, and 3 domains.

First session

1. Create an account and open Domains.
2. Add the domain you will send from, such as yourdomain.com.
3. Publish the DNS records from the domain card. The apex SPF row is optional.
4. Press Verify. When Amazon finishes DKIM, the status pill changes to Verified and the owners get a ready email.
5. Open API keys, create a sending key, and send one message to yourself.

Send the first message

Replace the host if you are on a local Pigeon at http://localhost:4005. From has to be a verified domain, or a from address you verified on its own.

curl -X POST https://pigeonfs.com/api/emails \
  -H "Authorization: Bearer pg_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Ada <ada@yourdomain.com>",
    "to": ["you@yourdomain.com"],
    "subject": "Pigeon early test",
    "text": "If you can read this, the domain is sending."
  }'

Use case: a product welcome during the test

Point the signup handler at that same endpoint. Keep the key in the host's secret store. Watch Emails for the status, and Logs if the call is rejected. A 403 with domain_not_verified means the From host is still pending. A daily or monthly cap returns a quota error and the free plan stops until the window resets.

Without Amazon SES credentials, local Pigeon stores the message in the development mailbox instead of delivering it. Production sends through the SES account attached to Pigeon.