Minket sends and receives email through one API at https://api.minket.com/v1. It keeps a timeline of events for every email, delivers signed webhooks, manages your domains and their DNS, and runs contacts, broadcasts and automations. SDKs, a command line and an MCP server drive it from code, and the console runs it by hand. Send your first email to begin.

Guides

Start

  • Send your first email

    Authenticate with an API key, send an email, follow what happens to it, and the conventions every request shares.

  • Create and manage API keys

    Live and test keys, scopes, domain restrictions and rate limits, and creating, listing and revoking keys from the console, the API, the SDK and the command line.

  • Move a project from Resend

    Point the resend SDK at Minket with two environment variables, then move a project one step at a time with no downtime and a rollback that is one revert.

Sending

  • Send email with the API

    Single and batch sends, idempotency, attachments, tags, headers, scheduling, streams, suppressions, test mode, reading, sharing and metrics.

  • How an email is delivered

    What happens after an email is queued. The two-region failover, the ledger that never sends twice, what sent means, failure reasons, open and click tracking, and the Message-ID.

  • Build emails from templates

    Versioned templates with typed variables, built from blocks or uploaded HTML, previewed, published and sent by id or alias.

  • Send over SMTP

    SMTP credentials for Supabase auth and other SMTP clients, one per region, and what mail sent over SMTP skips.

  • Send as a person from a mailbox

    Send as a person through a connected Gmail, Microsoft 365 or SMTP mailbox, with copies in its Sent folder; OAuth consent, bring-your-own clients, reconnects.

Domains

  • Set up a sending domain

    Verify a sending domain. DKIM, MAIL FROM, staged DMARC, the authentication gate, tracking links, BIMI and automatic DNS on Cloudflare.

  • Protect your sender reputation

    Google Postmaster reputation and inbox-placement seed tests, what each needs before it shows anything, and how sending pauses when bounces or complaints climb.

  • Read DMARC reports

    Aggregate reports mailed to dmarc@ on a receiving domain, how they are checked, and the 30-day pass rate on each domain.

Events

  • Receive events by webhook

    Endpoints, event payloads, svix-compatible signatures with verification samples, retries, auto-disable, rotation, replay and test events.

  • Track events on the timeline

    Where events come from, how they move an email's status, and the event feed that lets you pull them with a cursor.

Receiving

  • Receive email on your domain

    Receive mail on your domains. Routing rules, envelope recipients, verdicts from SES, attachments, forwarding, limits and the receiving API.

Audience

  • Manage contacts and consent

    Contacts with typed properties, segments, topics, the consent ledger, double opt-in, CSV import and export, and sunsetting.

  • Let recipients unsubscribe

    The hosted unsubscribe page, RFC 8058 one-click unsubscribe, the preference center and double opt-in confirmation, with their signed tokens and what each records.

  • Send a broadcast to a segment

    Marketing sends to a segment or topic: drafts with blocks or HTML, consent at send time, scheduling, per-domain throttling, subject A/B tests, test sends, progress, analytics and cancel.

  • Automate email from events

    Event-triggered workflows that wait, send, branch on engagement or contact data and update contacts, with versions, runs and step history, through the API and the console builder.

Tools

  • Use the TypeScript, Python and Go SDKs

    The TypeScript SDK with resource methods, automatic idempotency keys and typed errors, and the generated Python and Go clients.

  • Work from the command line

    The minket command line: profiles with live and test keys, sending with attachments, domains, logs and events, webhooks, keys, templates from React Email, inbound mail, contact imports, and any operation with minket api.

  • Let an agent operate a project

    minket-mcp lets an agent such as Claude operate a project: domains, keys, logs and events, sending with a dry run, suppressions, webhook replays, received mail and contact lookups.

Organization

  • Manage members and roles

    Organizations, projects and environments, members and their roles, invitations, signing in through Cloudflare Access, and the audit log.

Reference

  • Error codes and retries

    Every error code with its status, whether it is retryable and its message, when to retry, and the request ids and logs that trace a failure.

  • Limits and retention

    Every product limit from the core limits table, where each kind applies, and how long content, metadata and logs are kept.

  • Resend compatibility reference

    What the compatibility layer mirrors of Resend's API, path by path, and where its shapes, errors, events and webhooks differ from Resend's.

Reference and tools

The API reference has every operation with its parameters, body, response and examples, under the names the SDKs, the command line and the MCP server use, generated from the OpenAPI document. Recipient pages (unsubscribe, preferences, opt-in) and tracking links are served from links.minket.com.

Updated