Connect Mailcheer to your tools
Five paths connect Mailcheer to your tools. Each one is described as it works: what it carries, and the safeguards that come with it.
The five paths
- File importA CSV exported from any tool — store, CRM, spreadsheet, or previous email platform. Three columns are recognized automatically: address, first name, last name. You label the batch as you go, decide whether existing contacts are updated, and the import reports back: imported, duplicates, invalid. How to import →
The most common path. Works whenever you update your list now and then. - The sign-up formA hosted sign-up page, under your workspace name — not ours: a link to put in your email signature, social bio, or behind a QR code. No website required. Forms in detail →
When your list grows on its own, which is the best way. - The public APIAn HTTP interface to send a single email, list and update subscribers, read your suppression list, create a campaign and send it. You authenticate with a key created under Settings → API, ticking rights one by one. The send fields match Resend's: migrating means updating the base URL and the key — and an invoice goes out with its PDF, through the
attachmentsfield. Every send then shows up in your workspace's Messages screen, with its status and, on a bounce, its reason. API reference →
When your own software writes to your users: invoices, alerts, password resets. - The MCP server, for AI agentsThe same mechanics, spoken by agents: Claude Code, ChatGPT, Codex, Cursor. One command to connect, thirteen tools exposed, and the same rights as the key — an agent cannot do anything you have not checked. No tool can empty the suppression list, and that is deliberate. Connect an agent →
When you would rather ask 'draft the September email' than open a screen. - The subscription endpoint for your siteAn address to use as the target of a plain HTML
<form>: it accepts JSON from a JavaScript-driven form as well as a regular form submit. That is what lets you connect a Webflow or WordPress site without writing a line of script. It carries the address, first name, last name and the custom fields your form asks for, applies the form's tags, and sends the confirmation email.
When sign-ups come from your own site, with no intermediary.
What happens when someone subscribes
Through either form, no one enters the list directly: a confirmation email goes out, and the address is only truly subscribed after the click. That is not a courtesy. Without it, a bot fills the list with dead addresses, bounces climb, and the sending account ends up suspended.
The API follows the same rule: a subscriber added by a program also enters as 'pending' and receives a confirmation. The shortcut exists — a field you write explicitly — but it is never the default, and whoever writes it in their code is responsible for consent, exactly like the checkbox on the file import.
File import enters directly: the screen asks you to confirm that these contacts have agreed to receive your emails, and you are responsible.
In both cases, an address that has unsubscribed or marked a message as spam never becomes active again — not through a form, not through a file that still contains it.
The safeguards
Every path has its own: email confirmation for the forms, rights ticked one by one for the API and agents, and for all of them, the suppression list.
Get started
File import brings in a list, the form grows it, the API connects your software. 3,000 sends a month free, no credit card.