メニュー
Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Deploy JavaScript functions to the MyAPI edge runtime (Cloudflare Workers). Register a function, upload a single-file JS bundle, get a live HTTP invocation URL or run it on a cron schedule. Each function gets a scoped capability key for cross-slot calls.
Take payments via Stripe — one-off or recurring. Connect your own Stripe account, then create hosted Stripe Checkout URLs. No raw card data ever touches your code.
Tracking pixel + identity resolution for MyAPI funnels and email. Capture visits and events, resolve known users to anonymous sessions, stream interaction events for analytics. Pairs with mycrmapi for auto-ingest of pixel_visit events on known contacts.
Auth, organizations, and billing hub. Start here to get an api_key and org_id — every other service depends on both.
Saved audiences = named Goldfox-filter snapshots over the people or company database. Build a target list once, name it, reuse it across campaigns, refresh to re-evaluate against current data. The persistence layer on top of my-people-api + my-company-api.
Register new domains and manage edge settings. Required before a funnel can go live on a custom URL.
| name | my-email-api |
| version | 1.0.0 |
| description | Send transactional and bulk email from your own domain. Create mailboxes, send/receive messages, generate AI templates, and manage warmup. |
| triggers | ["email","mailbox","send email","transactional email","template","warmup","inbox","outbox","ses","sender reputation"] |
| checksum | sha256-pending |
Account-scoped email infrastructure tied to your registered domains. Mailboxes belong to domains; sending and receiving work without per-org plumbing. Templates are org-scoped.
Email is built around mailboxes. Each mailbox lives on a registered domain (e.g. hello@yourdomain.com) and must be activated for sending before transactional sends work — newly-created mailboxes can receive but not send.
Templates are AI-generated HTML emails (org-scoped). Warmup is a separate flow that gradually ramps a mailbox's send rate to build inbox reputation before high-volume sending.
A registered domain via mydomainapi is the prerequisite — mailboxes need a domain to live on.
| Namespace | Subcommands | Purpose |
|---|---|---|
email mailbox | create, list, activate-sending | Create and manage mailboxes |
email message | send, status, sent, inbox, outbox, get | Transactional send + read |
email warmup | start, stats, pause, resume, stop | IP/domain warmup for sending reputation |
email template | generate, list, get, preview, edit, send-test, delete | AI-generated HTML templates |
# 1. Create a mailbox + activate sending
myapi email mailbox create hello@yourdomain.com --display-name "Hello"
myapi email mailbox activate-sending --address hello@yourdomain.com
# 2. Send a transactional email
myapi email message send \
--from hello@yourdomain.com --to recipient@example.com \
--subject "Hi" --body "Test message"
# 3. Read inbox / outbox
myapi email message inbox hello@yourdomain.com
myapi email message outbox hello@yourdomain.com
# 4. Generate + use a template
myapi email template generate welcome-v1 \
--prompt "A welcome email with our brand colors and a CTA to /onboarding"
myapi email template list
myapi email template preview <id> # public preview URL — share with stakeholders
myapi email template send-test <id> --to me@yourdomain.com
myapi email template edit <id> --prompt "Make the CTA larger and red"
# 5. Warm up before a big send
myapi email warmup start --address hello@yourdomain.com
myapi email warmup stats --address hello@yourdomain.com
username@domain).activate-sending runs.myapi config set-org <id>.Run myapi email --help or myapi email <namespace> --help for full flag reference.