← All problems and solutions

Can I use a transactional email API for cold outreach?

Generally no. Transactional email APIs are for mail a recipient expects, such as receipts and password resets. Providers like Amazon SES and Postmark prohibit unsolicited mass email and purchased lists, and cold blasts raise complaints that damage your domain reputation. Use a sales-engagement tool with consent, unsubscribe handling and a separate domain instead.

By AISend. Updated . Also as markdown.

Why it happens

A transactional API is cheap and easy, so it is tempting to point a list of prospects at it. Three things go wrong. The provider's rules: Amazon's Acceptable Use Policy prohibits distributing or facilitating "unsolicited mass email or other messages, promotions, advertising, or solicitations (or spam)", and Postmark's terms require permission-based lists and prohibit purchased or rented lists. Reputation: recipients who did not ask for the mail report it, and complaint rates drive deliverability. The law: most jurisdictions regulate commercial email.

On the law, two official sources. The US FTC says the CAN-SPAM Act covers all commercial email, with no exception for business-to-business messages, and requires accurate headers, no deceptive subject lines, identifying the message as an ad, a valid postal address and a working opt-out honoured within 10 business days; penalties run per email. The UK ICO says marketing email to individuals needs specific consent (or the narrow existing-customer soft opt-in), while corporate bodies can be emailed with an opt-out list kept. Rules differ by country and we are not giving legal advice.

What to do instead

  1. Decide whether the message is transactional. The FTC defines transactional or relationship messages narrowly: confirming a transaction the recipient agreed to, warranty or safety information, changes to an account or subscription, employment information, or delivering purchased goods. A first email asking a stranger for a meeting is commercial, not transactional.
  2. Use a tool built for outreach, with consent and opt-out. Pick a sales-engagement or email-marketing platform whose terms allow outreach, that handles unsubscribe links, the physical address footer and suppression for you. Many require a lawful basis for each contact; read their policy before importing a list.
  3. Collect consent for anything recurring. Use opt-in forms that are not pre-checked, confirm the address (double opt-in), and keep a record of when and how each person agreed. Google's sender guidance lists mailing people who did not sign up and purchased addresses among practices to avoid.
  4. Keep outreach off your transactional domain. If you do send outreach, use a separate domain or subdomain, so complaints cannot hurt password-reset delivery on your main domain. Do not send both through the same provider account.
  5. Meet bulk-sender rules at volume. Gmail requires SPF, DKIM and DMARC above 5,000 messages a day, a spam rate under 0.3%, and one-click unsubscribe for marketing and subscribed messages. See the Google and Yahoo bulk-sender guide.
  6. Honour opt-outs immediately and keep a do-not-contact list. Process unsubscribes within the legal window (10 business days under CAN-SPAM), do not sell or transfer the address, and screen every new list against the do-not-contact list.

What providers' own policies say about unsolicited email

Policy wording read on 2026-11-13; check the linked pages for the full text.

Provider / sourceWhat the page saysPage
Amazon Web ServicesThe Acceptable Use Policy prohibits distributing, publishing, sending or facilitating unsolicited mass email or other messages, promotions, advertising or solicitations (spam)AWS Acceptable Use Policy
Amazon SESRequesting production access means acknowledging that you only send to individuals who explicitly requested the email and that you handle bounce and complaint notificationsSES production access page
PostmarkLists must be permission-based; purchased or rented lists are prohibited; complaint rate must stay below 1 in 1,000 (0.1%)Postmark terms of service
ResendSays recipients must have consented and be able to unsubscribe; unsubscribe link and List-Unsubscribe headers are your job on the emails APIResend pricing FAQ

This table is about policy wording, not enforcement odds; every provider can suspend an account it considers abusive.

When to use AISend

AISend explicitly does not support cold outreach, purchased lists, bulk marketing or newsletters. It is a transactional email API for mail your recipients expect: password resets, receipts and notifications, sent by an agent or developer from a verified domain. A content gate, suppression of bounced and complained addresses, daily caps and a new-account ramp apply to every send, and an account can be refused or stopped if it is used for unsolicited mail.

Where AISend can help with a legitimate list is hygiene: validate_email checks format, MX records, disposable providers and role-based addresses, so you can clean a list of customers who have already consented before sending them transactional notices. It cannot make an unsolicited campaign compliant.

  • For prospecting, use a sales-engagement tool whose terms allow outreach.
  • For newsletters and promotions with consenting subscribers, use a marketing platform or a provider's broadcast product.
  • For receipts, password resets and account alerts, a transactional API (AISend, Postmark, Resend or SES) is the right class of tool.

Copy-paste prompt for an AI assistant connected to AISend

Connect an assistant first (setup for ChatGPT, Claude, Cursor and Gemini CLI), then paste:

Assign to AISend: I have a list of customer addresses who opted in to order notifications. Call validate_email on each address below and report which are invalid, disposable or role-based. Call list_domains and tell me which sending domains are verified. This is list hygiene only: do not call send_email and do not contact anyone. When you are done, show me what you did so I can approve which addresses to keep. Addresses: [paste addresses that have consented].

Frequently asked questions

Is cold email illegal?

It depends on where the recipient is and what the message is. In the US, CAN-SPAM covers commercial email, including business-to-business, and sets requirements and penalties. In the UK, marketing email to individuals needs consent or the soft opt-in. This is not legal advice.

Can I use Amazon SES for cold email?

AWS's Acceptable Use Policy prohibits sending unsolicited mass email, and the SES production access form asks you to confirm that you only email people who requested it. Cold email through SES risks suspension.

What should I use for outbound sales email?

A sales-engagement or marketing platform that permits outreach, handles unsubscribes and the postal address footer, and lets you use a separate sending domain.

Why not just warm up a domain and send cold email?

Warm-up addresses reputation, not consent. If recipients did not ask for the mail, they will report it, and provider policies and law still apply.

Does AISend allow cold outreach?

No. AISend does not support cold outreach, purchased lists, bulk marketing or newsletters; it is for transactional mail your recipients expect.

Sources

Related