<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Cresca</title>
    <description>The latest articles on DEV Community by Cresca (@crescadotxyz).</description>
    <link>https://dev.to/crescadotxyz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3378712%2Fdd6c21ab-0a93-4dc6-98c4-75391e0d42d8.png</url>
      <title>DEV Community: Cresca</title>
      <link>https://dev.to/crescadotxyz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/crescadotxyz"/>
    <language>en</language>
    <item>
      <title>Amazon Pinpoint Alternative for Email After the Shutdown</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Sat, 24 Oct 2026 07:57:39 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/amazon-pinpoint-alternative-for-email-after-the-shutdown-37ii</link>
      <guid>https://dev.to/crescadotxyz/amazon-pinpoint-alternative-for-email-after-the-shutdown-37ii</guid>
      <description>&lt;p&gt;&lt;strong&gt;AWS ends support for Amazon Pinpoint on October 30, 2026.&lt;/strong&gt; After that date the Pinpoint console and its engagement features, which are endpoints, segments, campaigns, journeys and analytics, can no longer be used. If you send email campaigns from Pinpoint, you need an Amazon Pinpoint alternative for your contacts, templates and campaigns before the deadline, and you need to export your data while you still can.&lt;/p&gt;

&lt;p&gt;This guide explains exactly what stops working, what keeps working, the paths AWS recommends, and a step-by-step plan to move your email to &lt;a href="https://www.cresca.xyz" rel="noopener noreferrer"&gt;Cresca&lt;/a&gt;, with scripts you can copy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;In this guide&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What stops on October 30, and what keeps working&lt;/li&gt;
&lt;li&gt;The paths AWS recommends&lt;/li&gt;
&lt;li&gt;Export your Pinpoint data first&lt;/li&gt;
&lt;li&gt;Where each Pinpoint feature goes in Cresca&lt;/li&gt;
&lt;li&gt;Step-by-step: move your email to Cresca&lt;/li&gt;
&lt;li&gt;If you only send transactional email through Pinpoint&lt;/li&gt;
&lt;li&gt;What Cresca does not replace&lt;/li&gt;
&lt;li&gt;A one-week migration checklist&lt;/li&gt;
&lt;li&gt;Frequently asked questions&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What stops on October 30, and what keeps working
&lt;/h2&gt;

&lt;p&gt;AWS's &lt;a href="https://docs.aws.amazon.com/pinpoint/latest/userguide/migrate.html" rel="noopener noreferrer"&gt;end-of-support notice&lt;/a&gt; splits Pinpoint into two halves. The &lt;strong&gt;engagement&lt;/strong&gt; features are retired. Several &lt;strong&gt;message-sending&lt;/strong&gt; APIs keep running. Pinpoint also stopped accepting new customers on May 20, 2025.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Pinpoint capability&lt;/th&gt;
&lt;th&gt;After October 30, 2026&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Console, endpoints, segments, campaigns, journeys&lt;/td&gt;
&lt;td&gt;No longer accessible&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Analytics and KPI APIs&lt;/td&gt;
&lt;td&gt;Not supported; export historical KPIs before the date&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;SendUsersMessages&lt;/code&gt; and sending to a stored endpoint ID&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;In-app messaging and recommenders&lt;/td&gt;
&lt;td&gt;Not supported&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email, SMS and voice sending with &lt;code&gt;SendMessages&lt;/code&gt;
&lt;/td&gt;
&lt;td&gt;Continues for existing customers only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email, SMS and voice templates&lt;/td&gt;
&lt;td&gt;Continue, including create, update and delete&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Push, push templates, OTP, phone number validation&lt;/td&gt;
&lt;td&gt;Continue for all accounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Event delivery to Kinesis or Data Firehose, metrics to CloudWatch&lt;/td&gt;
&lt;td&gt;Continue for direct sends&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The short version for email marketers: if you build audiences and send email campaigns or journeys in Pinpoint, that stops on October 30. If you only call &lt;code&gt;SendMessages&lt;/code&gt; to send one-off emails from your app, that keeps working for now, but AWS recommends moving it too.&lt;/p&gt;

&lt;h2&gt;
  
  
  The paths AWS recommends
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Email sending:&lt;/strong&gt; Amazon Simple Email Service (SES). SES is a sending service. It has no campaign builder, audience segments or email designer, so you build those yourself or use a platform on top.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Segments, campaigns and journeys:&lt;/strong&gt; Amazon Connect outbound campaigns and Customer Profiles. This path is built for contact-centre teams: agent-assisted calling, predictive dialling and coordinated inbound and outbound engagement.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;SMS, voice, push and OTP:&lt;/strong&gt; AWS End User Messaging, which is what Pinpoint's channel APIs were renamed to in 2024.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Events and mobile analytics:&lt;/strong&gt; Amazon Kinesis.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The email deliverability dashboard:&lt;/strong&gt; SES Virtual Deliverability Manager.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your Pinpoint use was mostly &lt;em&gt;email marketing&lt;/em&gt;, meaning a contact list, a few segments, designed campaigns and maybe a welcome series, neither SES on its own nor a contact-centre platform is a like-for-like replacement. That's the gap an email marketing platform fills as an Amazon Pinpoint alternative.&lt;/p&gt;

&lt;h2&gt;
  
  
  Export your Pinpoint data first
&lt;/h2&gt;

&lt;p&gt;Do this before anything else, while the console still works. Everything below comes from the AWS offboarding steps.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Endpoints (your contacts).&lt;/strong&gt; Create a segment with no filters, so it includes every endpoint, then export it to an S3 bucket or download it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Segments, campaigns and journeys.&lt;/strong&gt; Save their definitions with the &lt;code&gt;get-segment&lt;/code&gt;, &lt;code&gt;get-campaign&lt;/code&gt; and &lt;code&gt;get-journey&lt;/code&gt; APIs, or copy them from the console. You'll rebuild them, so screenshots of the important ones help too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Templates.&lt;/strong&gt; List them with &lt;code&gt;list-templates&lt;/code&gt;, then fetch each one with &lt;code&gt;get-email-template&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Analytics.&lt;/strong&gt; The KPI APIs, such as &lt;code&gt;get-campaign-date-range-kpi&lt;/code&gt; and &lt;code&gt;get-application-date-range-kpi&lt;/code&gt;, return up to the past 3 months. Export anything you want to keep for reporting.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;For example, with the AWS CLI:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Save every email template&lt;/span&gt;
aws pinpoint list-templates &lt;span class="nt"&gt;--template-type&lt;/span&gt; EMAIL &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; templates.json
aws pinpoint get-email-template &lt;span class="nt"&gt;--template-name&lt;/span&gt; welcome-email &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; welcome-email.json

&lt;span class="c"&gt;# Save a campaign definition and its last 3 months of KPIs&lt;/span&gt;
aws pinpoint get-campaign &lt;span class="nt"&gt;--application-id&lt;/span&gt; APP_ID &lt;span class="nt"&gt;--campaign-id&lt;/span&gt; CAMPAIGN_ID &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; campaign.json
aws pinpoint get-campaign-date-range-kpi &lt;span class="nt"&gt;--application-id&lt;/span&gt; APP_ID &lt;span class="nt"&gt;--campaign-id&lt;/span&gt; CAMPAIGN_ID &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;--kpi-name&lt;/span&gt; email-open-rate &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; campaign-kpi.json
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Cresca as an Amazon Pinpoint alternative: where each feature goes
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;In Pinpoint&lt;/th&gt;
&lt;th&gt;In Cresca&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Email endpoints&lt;/td&gt;
&lt;td&gt;Contacts, imported from CSV or added with the contacts API&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Endpoint and user attributes&lt;/td&gt;
&lt;td&gt;Custom fields and tags&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Segments&lt;/td&gt;
&lt;td&gt;Contact lists, built from tags and custom fields&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email campaigns&lt;/td&gt;
&lt;td&gt;Campaigns: designed by the AI agent, in the design editor or from a template, sent now or scheduled&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Simple email journeys, such as a welcome series&lt;/td&gt;
&lt;td&gt;Automation workflows that send a sequence of emails with delays&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Email templates&lt;/td&gt;
&lt;td&gt;Marketing templates in the design editor; transactional templates with versions for API email&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;SendMessages&lt;/code&gt; for app email&lt;/td&gt;
&lt;td&gt;The transactional email API: &lt;code&gt;POST /emails&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Campaign analytics&lt;/td&gt;
&lt;td&gt;Campaign reports: deliveries, bounces, complaints, unsubscribes, plus opt-in opens and clicks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Verified email identity on SES&lt;/td&gt;
&lt;td&gt;A verified sending domain in Cresca, with its own DKIM and SPF records&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Step-by-step: move your email to Cresca
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Step 1: Verify your sending domain
&lt;/h3&gt;

&lt;p&gt;In Cresca, open Sending Domains and add the domain you send from today. Cresca gives you the exact DNS records: an ownership record, three DKIM records and a custom MAIL FROM subdomain with its own SPF record. If your DNS is on Cloudflare, Cresca can add them for you.&lt;/p&gt;

&lt;p&gt;Your existing SES records can stay where they are. Cresca only adds new records and never overwrites existing ones, so your Pinpoint sending keeps working while you test. See &lt;a href="https://www.cresca.xyz/sending-domains" rel="noopener noreferrer"&gt;sending domains&lt;/a&gt; for details.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Turn your endpoint export into a clean contact file
&lt;/h3&gt;

&lt;p&gt;A Pinpoint segment export has one endpoint per line, including SMS and push endpoints, and opted-out addresses. Before importing, keep only email endpoints, &lt;strong&gt;leave out anyone who opted out&lt;/strong&gt;, and remove duplicates. This script does that and writes a CSV you can import:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;csv&lt;/span&gt;
&lt;span class="kn"&gt;import&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;first&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;values&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="sh"&gt;"""&lt;/span&gt;&lt;span class="s"&gt;Pinpoint stores attributes as lists of strings.&lt;/span&gt;&lt;span class="sh"&gt;"""&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;values&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="nf"&gt;isinstance&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;values&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;list&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="n"&gt;values&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="sh"&gt;""&lt;/span&gt;

&lt;span class="n"&gt;seen&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;set&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="k"&gt;with&lt;/span&gt; &lt;span class="nf"&gt;open&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;pinpoint-endpoints.json&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;src&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;open&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;cresca-contacts.csv&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;w&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;newline&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="sh"&gt;""&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;writer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;csv&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;writer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;writer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;writerow&lt;/span&gt;&lt;span class="p"&gt;([&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;email&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;first_name&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;last_name&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;plan&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;line&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;src&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="n"&gt;endpoint&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;json&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;loads&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;line&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;endpoint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ChannelType&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;EMAIL&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;continue&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;endpoint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;OptOut&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;ALL&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;      &lt;span class="c1"&gt;# opted out: do not import
&lt;/span&gt;            &lt;span class="k"&gt;continue&lt;/span&gt;
        &lt;span class="n"&gt;email&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;endpoint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Address&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="sh"&gt;""&lt;/span&gt;&lt;span class="p"&gt;).&lt;/span&gt;&lt;span class="nf"&gt;strip&lt;/span&gt;&lt;span class="p"&gt;().&lt;/span&gt;&lt;span class="nf"&gt;lower&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="n"&gt;email&lt;/span&gt; &lt;span class="ow"&gt;or&lt;/span&gt; &lt;span class="n"&gt;email&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;seen&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;continue&lt;/span&gt;
        &lt;span class="n"&gt;seen&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
        &lt;span class="n"&gt;user&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;endpoint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;User&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{}).&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;UserAttributes&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{})&lt;/span&gt;
        &lt;span class="n"&gt;attrs&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;endpoint&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Attributes&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{})&lt;/span&gt;
        &lt;span class="n"&gt;writer&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;writerow&lt;/span&gt;&lt;span class="p"&gt;([&lt;/span&gt;
            &lt;span class="n"&gt;email&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="nf"&gt;first&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;FirstName&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)),&lt;/span&gt;
            &lt;span class="nf"&gt;first&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;LastName&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)),&lt;/span&gt;
            &lt;span class="nf"&gt;first&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;attrs&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;get&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;Plan&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)),&lt;/span&gt;           &lt;span class="c1"&gt;# any custom attribute you use
&lt;/span&gt;        &lt;span class="p"&gt;])&lt;/span&gt;

&lt;span class="nf"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="nf"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;seen&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt; contacts written&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Change the attribute names to the ones your project uses. Anything you used for segmenting, such as plan, country or signup date, is worth keeping as a column.&lt;/p&gt;

&lt;p&gt;Opted-out people must stay out of your marketing. Don't import them as contacts. If you want an extra safeguard, add their addresses to your suppression list in Cresca.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Import your contacts
&lt;/h3&gt;

&lt;p&gt;Import the CSV in Contacts, map each column to a field or custom field, and add tags that match your old segments. During import, invalid and duplicate addresses are skipped, and addresses that have bounced or complained are kept out.&lt;/p&gt;

&lt;p&gt;If you'd rather script it, the contacts API adds up to 1,000 contacts per request to a list, creating the list if needed. It takes an email address and an optional first and last name, so use the CSV import for custom fields.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://api.cresca.xyz/api/v1/contacts&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;Authorization&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`Bearer &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;CRESCA_API_KEY&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="c1"&gt;// full-access key&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;list_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Migrated from Pinpoint&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;contacts&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;email&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;ana@example.com&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;first_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Ana&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
      &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;email&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;ben@example.com&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;first_name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Ben&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
    &lt;span class="p"&gt;],&lt;/span&gt;
  &lt;span class="p"&gt;}),&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;span class="nx"&gt;console&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;log&lt;/span&gt;&lt;span class="p"&gt;((&lt;/span&gt;&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nx"&gt;response&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;json&lt;/span&gt;&lt;span class="p"&gt;()).&lt;/span&gt;&lt;span class="nx"&gt;summary&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt; &lt;span class="c1"&gt;// created, updated, rejected...&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Contact imports through the API are limited to 120 requests per 15 minutes, on top of your plan's general rate limit. Check your plan's contact limit on the &lt;a href="https://www.cresca.xyz/pricing" rel="noopener noreferrer"&gt;pricing page&lt;/a&gt; before you start.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 4: Rebuild your segments as lists
&lt;/h3&gt;

&lt;p&gt;Go through the segment definitions you saved and rebuild the ones you still use as contact lists, using the tags and custom fields from your import. This is a good moment to drop segments nobody has sent to in months.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Rebuild your templates and campaigns
&lt;/h3&gt;

&lt;p&gt;Pinpoint templates use Handlebars placeholders such as &lt;code&gt;{{User.UserAttributes.FirstName}}&lt;/code&gt;. Replace them with Cresca merge fields for the matching contact fields.&lt;/p&gt;

&lt;p&gt;You don't have to copy every old design by hand. Describe the campaign to Cresca's AI agent, such as "Our monthly product update for existing customers, three short sections, plain and friendly", and it designs a complete email using your brand profile. A fact-check pass removes claims your brief didn't make. Then fine-tune it in the design editor, or start from one of 36 templates.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 6: Recreate simple journeys
&lt;/h3&gt;

&lt;p&gt;If a journey was a straight email sequence, such as a welcome series of three emails a few days apart, rebuild it as an automation workflow. Journeys that branched across channels or used push and SMS steps don't have a direct equivalent in Cresca; keep the non-email parts on AWS End User Messaging.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 7: Warm up, then switch
&lt;/h3&gt;

&lt;p&gt;Send your first Cresca campaigns to your most engaged contacts, the people who opened or clicked recently, then widen the audience over a week or two. A sudden jump in volume from new sending records can look suspicious to mailbox providers. Our &lt;a href="https://www.cresca.xyz/blog/domain-warmup-guide" rel="noopener noreferrer"&gt;domain warm-up guide&lt;/a&gt; covers the schedule. Once the new setup is working, stop the old Pinpoint campaigns.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you only send transactional email through Pinpoint
&lt;/h2&gt;

&lt;p&gt;If your app calls &lt;code&gt;SendMessages&lt;/code&gt; for password resets, receipts or verification codes, that keeps working after October 30 for existing customers. But it's a good time to move, and the change is small. With Cresca's transactional email API, one request sends an email from your verified domain:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-X&lt;/span&gt; POST &lt;span class="s1"&gt;'https://api.cresca.xyz/api/v1/emails'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'Authorization: Bearer cr_live_xxxxxxxxx'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'Content-Type: application/json'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-H&lt;/span&gt; &lt;span class="s1"&gt;'Idempotency-Key: password-reset/req_8f2a'&lt;/span&gt; &lt;span class="se"&gt;\&lt;/span&gt;
  &lt;span class="nt"&gt;-d&lt;/span&gt; &lt;span class="s1"&gt;'{
  "from": "Acme &amp;lt;hello@acme.com&amp;gt;",
  "to": "user@example.com",
  "subject": "Reset your password",
  "html": "&amp;lt;p&amp;gt;Click the link to reset your password. It expires in 1 hour.&amp;lt;/p&amp;gt;"
}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;What you get that a bare send API doesn't give you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Templates with versions.&lt;/strong&gt; Move your Pinpoint email templates into Cresca, publish them, and send by alias with &lt;code&gt;{{{VARIABLE}}}&lt;/code&gt; values. Editing a draft never changes what your app sends.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Safe retries.&lt;/strong&gt; The same &lt;code&gt;Idempotency-Key&lt;/code&gt; and body within 24 hours returns the original response instead of sending twice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The right suppression rules.&lt;/strong&gt; A marketing unsubscribe never blocks a password reset, while hard bounces and spam complaints do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A log for every email,&lt;/strong&gt; with a per-recipient timeline, kept for 30 days.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The same account as your campaigns,&lt;/strong&gt; with one domain setup and one monthly email allowance.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://www.cresca.xyz/docs/quickstart" rel="noopener noreferrer"&gt;quickstart&lt;/a&gt; takes you from a verified domain to a first email, and the &lt;a href="https://www.cresca.xyz/blog/transactional-email-api" rel="noopener noreferrer"&gt;transactional email API guide&lt;/a&gt; covers every endpoint with code.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Cresca does not replace
&lt;/h2&gt;

&lt;p&gt;Pinpoint did more than email, so be clear about what moves where:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SMS, voice, push and OTP:&lt;/strong&gt; Cresca is email only. Keep these on AWS End User Messaging, where the Pinpoint channel APIs already live.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;In-app messaging:&lt;/strong&gt; not offered by Cresca, and not supported by AWS after October 30 either.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Event streaming and mobile analytics:&lt;/strong&gt; move these to Amazon Kinesis.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Webhooks and SMTP:&lt;/strong&gt; Cresca's API doesn't offer outbound webhooks or an SMTP relay yet. Check delivery with the API or in the dashboard.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A/B testing:&lt;/strong&gt; not offered in Cresca today.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  A one-week migration checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Day 1:&lt;/strong&gt; Export endpoints, segment, campaign and journey definitions, templates and the last 3 months of KPIs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 1:&lt;/strong&gt; Create a Cresca account and add your sending domain.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 2:&lt;/strong&gt; Publish the DNS records and verify the domain. Save your brand profile.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 2:&lt;/strong&gt; Clean the endpoint export with the script above and import it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 3:&lt;/strong&gt; Rebuild the segments you still use as lists.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 3–4:&lt;/strong&gt; Rebuild your main templates and campaigns, and send tests to yourself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 4:&lt;/strong&gt; Move transactional sends to &lt;code&gt;POST /emails&lt;/code&gt;, with an idempotency key.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Day 5 onwards:&lt;/strong&gt; Send to your most engaged contacts first, then widen the audience.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Before October 30:&lt;/strong&gt; Confirm nothing still depends on Pinpoint segments, campaigns or journeys.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  When does Amazon Pinpoint shut down?
&lt;/h3&gt;

&lt;p&gt;AWS ends support on October 30, 2026. After that, the Pinpoint console and its endpoints, segments, campaigns, journeys and analytics can no longer be used. Pinpoint stopped accepting new customers on May 20, 2025.&lt;/p&gt;

&lt;h3&gt;
  
  
  Will my Pinpoint emails stop sending?
&lt;/h3&gt;

&lt;p&gt;Campaigns and journeys stop, because they depend on the retired engagement features. Direct sends through the &lt;code&gt;SendMessages&lt;/code&gt; API continue for existing customers, though AWS recommends moving email to SES or another provider for the long term.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is the best Amazon Pinpoint alternative for email marketing?
&lt;/h3&gt;

&lt;p&gt;It depends on what you used Pinpoint for. For email campaigns, audiences and app email in one place, an email marketing platform such as Cresca replaces the engagement features, adds an AI email designer and keeps transactional email in the same account. For SMS and push, use AWS End User Messaging.&lt;/p&gt;

&lt;h3&gt;
  
  
  Can I keep my sending domain?
&lt;/h3&gt;

&lt;p&gt;Yes. Add the same domain in Cresca and publish its DNS records next to your existing ones. Cresca never overwrites existing records, so you can run both while you migrate.&lt;/p&gt;

&lt;h3&gt;
  
  
  What happens to people who opted out in Pinpoint?
&lt;/h3&gt;

&lt;p&gt;Leave them out of your import. An opt-out is still valid after you change platforms, and emailing those people again breaks their trust and, in many countries, the law.&lt;/p&gt;

&lt;h3&gt;
  
  
  How much does Cresca cost?
&lt;/h3&gt;

&lt;p&gt;Cresca is free for 30 days with no credit card. Paid plans are $29, $49 or $99 a month, sized by contacts and monthly emails, and every plan includes the transactional email API. See &lt;a href="https://www.cresca.xyz/pricing" rel="noopener noreferrer"&gt;pricing&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Start your migration today:&lt;/strong&gt; &lt;a href="https://app.cresca.xyz/signup" rel="noopener noreferrer"&gt;try Cresca free for 30 days&lt;/a&gt;, or go straight to the &lt;a href="https://www.cresca.xyz/docs/quickstart" rel="noopener noreferrer"&gt;API quickstart&lt;/a&gt; if you only need to move transactional email.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Originally published on the &lt;a href="https://www.cresca.xyz/blog/amazon-pinpoint-alternative" rel="noopener noreferrer"&gt;Cresca blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>email</category>
      <category>migration</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Your email API's next user is an AI agent. Here's what it needs</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Fri, 23 Oct 2026 04:35:47 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/your-email-apis-next-user-is-an-ai-agent-heres-what-it-needs-4an4</link>
      <guid>https://dev.to/crescadotxyz/your-email-apis-next-user-is-an-ai-agent-heres-what-it-needs-4an4</guid>
      <description>&lt;p&gt;If you ship an API in 2026, assume an AI agent will call it. Coding agents read your docs, write the request, read the error, fix it and try again, often with nobody watching.&lt;/p&gt;

&lt;p&gt;For most APIs that's fine. Email is different: a mistake goes straight to someone's inbox, and you can't take it back.&lt;/p&gt;

&lt;p&gt;Here are six things I think an email API needs before an agent uses it, and what we already have in &lt;a href="https://www.cresca.xyz" rel="noopener noreferrer"&gt;Cresca's&lt;/a&gt; API. I'll also cover what we don't have yet.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Docs a model can read in one go
&lt;/h2&gt;

&lt;p&gt;Agents don't click through a docs sidebar. They fetch a URL and read the text. So the docs need to work as plain text, with one page per endpoint and every field listed.&lt;/p&gt;

&lt;p&gt;We publish an &lt;a href="https://www.cresca.xyz/llms.txt" rel="noopener noreferrer"&gt;llms.txt&lt;/a&gt; file: a plain-text summary of what Cresca does, with links to the quickstart, the send endpoint, templates, idempotency, errors and rate limits. Point an agent at it, and it can find the right page without crawling the whole site.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Errors with a name, not just a message
&lt;/h2&gt;

&lt;p&gt;Agents fix their own mistakes by reading error responses. A message like "Something went wrong" gives them nothing to work with. Every error from our API has the same shape:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"statusCode"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;403&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"invalid_from_address"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"The `from` address hello@acme.com is not an active sender on a verified domain. Add it under Sending domains in Cresca."&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The &lt;code&gt;name&lt;/code&gt; is stable, so code (or an agent) can branch on it. The &lt;code&gt;message&lt;/code&gt; says what to do next: an agent that gets this error knows to switch to a verified sender instead of retrying the same request.&lt;/p&gt;

&lt;p&gt;The names an agent meets most: &lt;code&gt;missing_api_key&lt;/code&gt;, &lt;code&gt;invalid_api_key&lt;/code&gt;, &lt;code&gt;restricted_api_key&lt;/code&gt;, &lt;code&gt;invalid_from_address&lt;/code&gt;, &lt;code&gt;validation_error&lt;/code&gt;, &lt;code&gt;missing_required_field&lt;/code&gt; and &lt;code&gt;rate_limit_exceeded&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Retries that can't send twice
&lt;/h2&gt;

&lt;p&gt;Agents retry a lot. A timeout, an unclear response or a restarted task, and the same request goes out again. With email, that means a customer gets two receipts.&lt;/p&gt;

&lt;p&gt;The fix is an &lt;code&gt;Idempotency-Key&lt;/code&gt; header. Use the same key and the same body within 24 hours, and you get the original response back instead of a second email. Tell the agent to build the key from the event, not from a timestamp:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Idempotency-Key&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;`order-receipt/&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;order&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two more cases an agent needs to handle: the same key with a different body returns &lt;code&gt;409 invalid_idempotent_request&lt;/code&gt;, and the same key while the first request is still running returns &lt;code&gt;409 concurrent_idempotent_requests&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Keys that can only do one thing
&lt;/h2&gt;

&lt;p&gt;Don't give an agent your admin key. Give it the smallest key that does the job.&lt;/p&gt;

&lt;p&gt;Our API has two kinds of key. A &lt;strong&gt;sending-access&lt;/strong&gt; key can call &lt;code&gt;POST /emails&lt;/code&gt; and &lt;code&gt;POST /emails/batch&lt;/code&gt;, nothing else, and you can limit it to one verified domain. A &lt;strong&gt;full-access&lt;/strong&gt; key can also read, cancel and manage templates and contacts. If an agent with a sending key tries anything else, it gets &lt;code&gt;401 restricted_api_key&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;So even if an agent misbehaves, or a prompt injection tricks it, it can't read your email logs or send from a domain you didn't give it.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Templates instead of HTML
&lt;/h2&gt;

&lt;p&gt;Letting an agent write the HTML of a password reset is asking for trouble: broken markup, a missing link, a made-up promise.&lt;/p&gt;

&lt;p&gt;A template is safer. A person designs the email once and publishes it, and the agent only fills in values:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="k"&gt;await&lt;/span&gt; &lt;span class="nf"&gt;fetch&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;https://api.cresca.xyz/api/v1/emails&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="na"&gt;method&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;POST&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="na"&gt;headers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="na"&gt;Authorization&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`Bearer &lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;process&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;env&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;CRESCA_SENDING_KEY&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Content-Type&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;application/json&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;Idempotency-Key&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;`password-reset/&lt;/span&gt;&lt;span class="p"&gt;${&lt;/span&gt;&lt;span class="nx"&gt;resetRequest&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="s2"&gt;`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="na"&gt;body&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;
    &lt;span class="na"&gt;to&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;email&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;template&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;password-reset&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;variables&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="na"&gt;NAME&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;user&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;name&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="na"&gt;RESET_URL&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nx"&gt;resetUrl&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="p"&gt;},&lt;/span&gt;
  &lt;span class="p"&gt;}),&lt;/span&gt;
&lt;span class="p"&gt;});&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Values are HTML-escaped, so they can't change the markup. And if the agent forgets a variable that has no fallback, the API returns &lt;code&gt;422 validation_error&lt;/code&gt; naming the missing variable instead of sending a broken email.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Limits it can read
&lt;/h2&gt;

&lt;p&gt;Agents are fast and don't get tired, so they hit rate limits. The response should tell them how long to wait. Ours returns &lt;code&gt;429 rate_limit_exceeded&lt;/code&gt; with a &lt;code&gt;retry-after&lt;/code&gt; header in seconds. The limits are per account: 2 requests per second on the Free plan, up to 100 on Enterprise.&lt;/p&gt;

&lt;p&gt;One more limit to teach an agent: &lt;code&gt;monthly_quota_exceeded&lt;/code&gt; is also a 429, but waiting won't fix it. Tell it to stop and report back instead of retrying.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tool definition
&lt;/h2&gt;

&lt;p&gt;Put all of that together and the tool you give the agent is small. Here's a provider-neutral version:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"send_password_reset"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Send the published password-reset email to one user. Never call this twice for the same reset request."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"input_schema"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"object"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"properties"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"to"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"The user's email address"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"reset_url"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
      &lt;/span&gt;&lt;span class="nl"&gt;"reset_request_id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"string"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="nl"&gt;"description"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"Used as the idempotency key"&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="p"&gt;},&lt;/span&gt;&lt;span class="w"&gt;
    &lt;/span&gt;&lt;span class="nl"&gt;"required"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"to"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"reset_url"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"reset_request_id"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Notice what the agent doesn't control: the sender, the subject, the HTML or the key. Your code fills those in. The agent decides &lt;em&gt;when&lt;/em&gt; to send and &lt;em&gt;to whom&lt;/em&gt;, and nothing else.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we don't have yet
&lt;/h2&gt;

&lt;p&gt;To be honest about the gaps:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;No MCP server yet.&lt;/strong&gt; Today an agent uses the plain REST API, which works with any agent that can make an HTTP request.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;No webhooks yet.&lt;/strong&gt; An agent checks delivery with &lt;code&gt;GET /emails/:id&lt;/code&gt;, which returns the latest status as &lt;code&gt;last_event&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Unknown fields are ignored, not rejected.&lt;/strong&gt; That's forgiving for people, but an agent that invents a field won't get an error. Validate the payload in your tool before you send it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Your turn
&lt;/h2&gt;

&lt;p&gt;If you've let an agent call an API that can't take back its mistakes, such as email, payments or deploys, what guardrails did you add? I'd especially like to hear what went wrong the first time.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>api</category>
      <category>email</category>
      <category>discuss</category>
    </item>
    <item>
      <title>How our AI agent turns a one-line brief into a responsive email template</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Sun, 11 Oct 2026 17:51:51 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/how-our-ai-agent-turns-a-one-line-brief-into-a-responsive-email-template-2ank</link>
      <guid>https://dev.to/crescadotxyz/how-our-ai-agent-turns-a-one-line-brief-into-a-responsive-email-template-2ank</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcik8o2gt1xn58ejmpaa0.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcik8o2gt1xn58ejmpaa0.png" alt="Cresca AI agent: a written brief on the left, the generated email with live preview on the right" width="800" height="395"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Anyone who has hand-coded a marketing email knows the pain: nested tables, inline styles, buttons that break in Outlook, images that look fine on desktop and terrible on a phone. Most small teams solve it by reusing the same tired template forever.&lt;/p&gt;

&lt;p&gt;We built the Cresca AI agent to fix that part of the job. You describe the email you want in plain words, and it builds a complete, editable email: layout, copy, sections and a clear call to action, ready to preview and send.&lt;/p&gt;

&lt;h3&gt;
  
  
  What it looks like
&lt;/h3&gt;

&lt;p&gt;You type a brief into &lt;strong&gt;Message Cresca AI&lt;/strong&gt;, for example:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Create a welcome email for new subscribers. Thank them, give the code HELLO10 for 10% off the first order, tell our story in two lines, and mention they can reply anytime for help.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;A few seconds later you have a full email in the &lt;strong&gt;email studio&lt;/strong&gt;: the conversation on the left, a live preview on the right.&lt;/p&gt;

&lt;h3&gt;
  
  
  Refine it like you'd brief a designer
&lt;/h3&gt;

&lt;p&gt;The first draft is a starting point, not a final answer. You keep talking to the agent in the same conversation:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;"Make it shorter."&lt;/li&gt;
&lt;li&gt;"Use a warmer tone."&lt;/li&gt;
&lt;li&gt;"Add a section with three product picks."&lt;/li&gt;
&lt;li&gt;"Make the button say &lt;em&gt;Claim my 10%&lt;/em&gt;."&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Each change updates the preview, so you can see the result before you commit to it.&lt;/p&gt;

&lt;h3&gt;
  
  
  On brand by default
&lt;/h3&gt;

&lt;p&gt;Generic AI output usually looks generic. So the agent works from a &lt;strong&gt;brand profile&lt;/strong&gt;: your brand name, website, logo and brand color, which it uses for buttons and banners. You can also drop in your own photos. Set it up once, and every email starts looking like you.&lt;/p&gt;

&lt;h3&gt;
  
  
  Built for the inbox, not just the screenshot
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Desktop and mobile preview&lt;/strong&gt;, side by side with the conversation, so you catch layout problems before your subscribers do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Studio view&lt;/strong&gt; for a closer look at the full design.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Copy HTML&lt;/strong&gt; if you want the code for another tool.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Save as a template&lt;/strong&gt; and reuse it in campaigns.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Tips for better results
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;One email, one goal.&lt;/strong&gt; Say what you want people to do.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Give the facts.&lt;/strong&gt; Paste prices, dates and codes exactly; the agent should never have to guess.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Show your voice.&lt;/strong&gt; A sentence from an email you've sent before helps more than "friendly but professional".&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review before you send.&lt;/strong&gt; AI drafts can get details wrong. You stay in charge of what goes out.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Try it
&lt;/h3&gt;

&lt;p&gt;The AI agent is included on every Cresca plan, and you can try it free for 30 days with no credit card: &lt;a href="https://www.cresca.xyz" rel="noopener noreferrer"&gt;cresca.xyz&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;What's the most painful part of building emails for you? I'd love to hear in the comments.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>emailmarketing</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to Set Up a Sending Domain for Email Marketing and Transactional Email</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Wed, 07 Oct 2026 18:28:23 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/how-to-set-up-a-sending-domain-for-email-marketing-and-transactional-email-36j8</link>
      <guid>https://dev.to/crescadotxyz/how-to-set-up-a-sending-domain-for-email-marketing-and-transactional-email-36j8</guid>
      <description>&lt;p&gt;Sending an email is easy.&lt;/p&gt;

&lt;p&gt;Sending &lt;strong&gt;millions of emails reliably from your own domain&lt;/strong&gt; is a completely different problem.&lt;/p&gt;

&lt;p&gt;If you've ever built a SaaS product, an email marketing platform, a newsletter system, or a transactional email service, you've probably encountered terms like &lt;strong&gt;SPF, DKIM, DMARC, DNS, sender identity, email authentication, and domain reputation&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;These aren't just configuration details.&lt;/p&gt;

&lt;p&gt;They are part of the foundation that determines whether your emails are trusted, delivered, or filtered into spam.&lt;/p&gt;

&lt;p&gt;In this guide, we'll break down how sending domains work, why they matter, and what you need to configure before sending emails from your own domain.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Is a Sending Domain?
&lt;/h2&gt;

&lt;p&gt;A sending domain is the domain you use as the identity for outgoing emails.&lt;/p&gt;

&lt;p&gt;For example, imagine your company owns:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You may want to send emails from:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;hello@example.com
marketing@example.com
notifications@example.com
support@example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Instead of using a generic provider address, your application sends email using your own domain.&lt;/p&gt;

&lt;p&gt;This gives you control over your email identity and allows you to configure authentication specifically for your domain.&lt;/p&gt;

&lt;p&gt;For an email marketing platform, a sending domain is especially important because campaigns should represent the business sending them.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Should You Use Your Own Sending Domain?
&lt;/h2&gt;

&lt;p&gt;There are several reasons to configure a dedicated sending domain.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Brand consistency
&lt;/h3&gt;

&lt;p&gt;Customers should recognize who sent an email before they even open it.&lt;/p&gt;

&lt;p&gt;Compare:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;newsletter@yourcompany.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;with an unfamiliar generic sending address.&lt;/p&gt;

&lt;p&gt;Your domain becomes part of your brand identity.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Email authentication
&lt;/h3&gt;

&lt;p&gt;Your domain can be configured with authentication mechanisms such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SPF&lt;/li&gt;
&lt;li&gt;DKIM&lt;/li&gt;
&lt;li&gt;DMARC&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;These help receiving mail systems evaluate whether messages are authorized and whether the sender's identity is trustworthy.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Better control
&lt;/h3&gt;

&lt;p&gt;When you're building an email infrastructure, controlling your sending domain gives you more visibility into:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Authentication&lt;/li&gt;
&lt;li&gt;Sending identities&lt;/li&gt;
&lt;li&gt;Domain configuration&lt;/li&gt;
&lt;li&gt;Reputation&lt;/li&gt;
&lt;li&gt;Delivery events&lt;/li&gt;
&lt;li&gt;Bounce handling&lt;/li&gt;
&lt;li&gt;Complaint handling&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4. Separation of email traffic
&lt;/h3&gt;

&lt;p&gt;You may not want every type of email to share exactly the same infrastructure.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;marketing.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;could be used for campaigns while:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;mail.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;could be used for application notifications.&lt;/p&gt;

&lt;p&gt;The right architecture depends on your product, volume, and reputation strategy.&lt;/p&gt;




&lt;h1&gt;
  
  
  How Email Authentication Works
&lt;/h1&gt;

&lt;p&gt;When you send an email, the receiving mail server doesn't simply trust the &lt;code&gt;From&lt;/code&gt; address.&lt;/p&gt;

&lt;p&gt;It can check DNS records and other authentication signals to determine whether the message is actually authorized.&lt;/p&gt;

&lt;p&gt;Three of the most important technologies are:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;SPF&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DKIM&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;DMARC&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Let's look at each one.&lt;/p&gt;




&lt;h2&gt;
  
  
  SPF: Sender Policy Framework
&lt;/h2&gt;

&lt;p&gt;SPF allows a domain owner to publish a DNS record specifying which mail servers are authorized to send email on behalf of that domain.&lt;/p&gt;

&lt;p&gt;A simplified example looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;example.com TXT
v=spf1 include:mail-provider.example ~all
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The exact record depends on the email infrastructure you're using.&lt;/p&gt;

&lt;p&gt;When a receiving server gets an email, it can check the sending server's IP address against the domain's SPF policy.&lt;/p&gt;

&lt;p&gt;If the server isn't authorized, the message may fail SPF evaluation.&lt;/p&gt;

&lt;h3&gt;
  
  
  Important SPF limitation
&lt;/h3&gt;

&lt;p&gt;SPF has a DNS lookup limit.&lt;/p&gt;

&lt;p&gt;If you keep adding providers and &lt;code&gt;include&lt;/code&gt; statements without considering the lookup limit, your SPF configuration can eventually fail.&lt;/p&gt;

&lt;p&gt;This is one reason email infrastructure should be designed carefully instead of continuously adding DNS records whenever a new provider is introduced.&lt;/p&gt;




&lt;h1&gt;
  
  
  DKIM: DomainKeys Identified Mail
&lt;/h1&gt;

&lt;p&gt;DKIM adds a cryptographic signature to outgoing email.&lt;/p&gt;

&lt;p&gt;The sending system signs the message with a private key.&lt;/p&gt;

&lt;p&gt;The corresponding public key is published through DNS.&lt;/p&gt;

&lt;p&gt;A simplified DKIM DNS record might look like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;selector1._domainkey.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;with a value containing the public key.&lt;/p&gt;

&lt;p&gt;When the email arrives, the receiving server can retrieve the public key and verify the signature.&lt;/p&gt;

&lt;p&gt;This helps establish that the message was authorized by the domain associated with the DKIM signature and that important parts of the message haven't been modified after signing.&lt;/p&gt;

&lt;p&gt;DKIM is particularly important when building a production email sending system.&lt;/p&gt;




&lt;h1&gt;
  
  
  DMARC: Domain-based Message Authentication
&lt;/h1&gt;

&lt;p&gt;DMARC builds on SPF and DKIM.&lt;/p&gt;

&lt;p&gt;It allows domain owners to publish a policy describing how receiving servers should handle messages that don't properly authenticate.&lt;/p&gt;

&lt;p&gt;A basic DMARC record looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;_dmarc.example.com TXT
v=DMARC1; p=none
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A domain can gradually move toward stricter policies as its email authentication is understood and monitored.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;p=none
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;can be useful during monitoring.&lt;/p&gt;

&lt;p&gt;More restrictive policies can then be introduced after validating legitimate sending sources.&lt;/p&gt;

&lt;p&gt;The important part is not simply adding a DMARC record.&lt;/p&gt;

&lt;p&gt;You need to understand &lt;strong&gt;which systems are legitimately sending email for your domain&lt;/strong&gt; before enforcing a strict policy.&lt;/p&gt;




&lt;h1&gt;
  
  
  The DNS Setup
&lt;/h1&gt;

&lt;p&gt;When adding a sending domain to an email platform, you'll typically receive DNS records to configure.&lt;/p&gt;

&lt;p&gt;These can include:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;TXT
CNAME
MX
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;depending on the provider and configuration.&lt;/p&gt;

&lt;p&gt;For example, an email platform might provide DKIM CNAME records such as:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;selector1._domainkey.example.com
selector2._domainkey.example.com
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Your DNS provider could be:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloudflare&lt;/li&gt;
&lt;li&gt;Route 53&lt;/li&gt;
&lt;li&gt;GoDaddy&lt;/li&gt;
&lt;li&gt;Namecheap&lt;/li&gt;
&lt;li&gt;Vercel DNS&lt;/li&gt;
&lt;li&gt;DigitalOcean&lt;/li&gt;
&lt;li&gt;Another domain provider&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The interface changes between providers, but the underlying DNS concepts remain the same.&lt;/p&gt;




&lt;h1&gt;
  
  
  A Typical Sending Domain Workflow
&lt;/h1&gt;

&lt;p&gt;A production email platform can make this process much simpler for users.&lt;/p&gt;

&lt;p&gt;The workflow can look like this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Add Domain
    ↓
Generate DNS Records
    ↓
User Adds DNS Records
    ↓
Verify DNS
    ↓
Validate Authentication
    ↓
Domain Ready
    ↓
Send Email
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This is the workflow we recently introduced in &lt;strong&gt;Cresca&lt;/strong&gt; with our new Sending Domains feature.&lt;/p&gt;




&lt;h1&gt;
  
  
  Sending Domains in Cresca
&lt;/h1&gt;

&lt;p&gt;We built Sending Domains because email infrastructure shouldn't require users to manually manage everything across multiple systems.&lt;/p&gt;

&lt;p&gt;Inside Cresca, users can add their domain and get the DNS configuration required for the sending setup.&lt;/p&gt;

&lt;p&gt;The general flow is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Cresca Dashboard
      ↓
Sending Domains
      ↓
Add Your Domain
      ↓
Configure DNS
      ↓
Verify Domain
      ↓
Start Sending
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Once the domain is verified, it can be used as part of the email sending setup.&lt;/p&gt;

&lt;p&gt;This is especially useful for teams using Cresca for:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Email marketing&lt;/li&gt;
&lt;li&gt;SaaS notifications&lt;/li&gt;
&lt;li&gt;Transactional emails&lt;/li&gt;
&lt;li&gt;Product updates&lt;/li&gt;
&lt;li&gt;Customer communication&lt;/li&gt;
&lt;li&gt;Automated campaigns&lt;/li&gt;
&lt;/ul&gt;




&lt;h1&gt;
  
  
  Marketing Email vs Transactional Email
&lt;/h1&gt;

&lt;p&gt;It's also important to understand that not all emails are the same.&lt;/p&gt;

&lt;h3&gt;
  
  
  Marketing emails
&lt;/h3&gt;

&lt;p&gt;Examples include:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Product announcements
Newsletters
Promotional campaigns
Product updates
Offers
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;These are generally sent to audiences for marketing purposes.&lt;/p&gt;

&lt;h3&gt;
  
  
  Transactional emails
&lt;/h3&gt;

&lt;p&gt;These are triggered by user or application actions.&lt;/p&gt;

&lt;p&gt;Examples:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Welcome emails
Password reset emails
Order confirmations
Payment receipts
Account notifications
Security alerts
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The infrastructure may overlap, but the sending strategy and reputation considerations can be different.&lt;/p&gt;

&lt;p&gt;For SaaS products, keeping your email architecture organized becomes increasingly important as sending volume grows.&lt;/p&gt;




&lt;h1&gt;
  
  
  Don't Ignore Bounce and Complaint Handling
&lt;/h1&gt;

&lt;p&gt;Domain authentication is only one part of email deliverability.&lt;/p&gt;

&lt;p&gt;You also need to pay attention to what happens &lt;strong&gt;after&lt;/strong&gt; an email is sent.&lt;/p&gt;

&lt;p&gt;For example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Email Sent
   ↓
Delivered
   ↓
Opened
   ↓
Clicked
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;But another path can be:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Email Sent
   ↓
Hard Bounce
   ↓
Suppress Address
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Or:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Email Sent
   ↓
Spam Complaint
   ↓
Suppress Address
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Continuing to send repeatedly to addresses that have permanently bounced is a bad strategy.&lt;/p&gt;

&lt;p&gt;A production email system should process delivery events and maintain suppression information.&lt;/p&gt;




&lt;h1&gt;
  
  
  Why Sending Reputation Matters
&lt;/h1&gt;

&lt;p&gt;Email providers don't evaluate your messages in isolation.&lt;/p&gt;

&lt;p&gt;Your sending behavior contributes to the reputation associated with your infrastructure and domains.&lt;/p&gt;

&lt;p&gt;Poor recipient quality can lead to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;High bounce rates&lt;/li&gt;
&lt;li&gt;Spam complaints&lt;/li&gt;
&lt;li&gt;Reduced deliverability&lt;/li&gt;
&lt;li&gt;Provider throttling&lt;/li&gt;
&lt;li&gt;Reputation problems&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This means email marketing isn't simply:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write email → Click Send
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A more realistic system looks like:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Audience
   ↓
Validation
   ↓
Authentication
   ↓
Sending
   ↓
Delivery Events
   ↓
Bounce / Complaint Processing
   ↓
Suppression
   ↓
Reputation Monitoring
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That entire feedback loop matters.&lt;/p&gt;




&lt;h1&gt;
  
  
  A Simple Production Checklist
&lt;/h1&gt;

&lt;p&gt;Before sending production email from a domain, check the following.&lt;/p&gt;

&lt;h3&gt;
  
  
  Domain
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Domain is owned and controlled by your organization&lt;/li&gt;
&lt;li&gt;[ ] DNS access is available&lt;/li&gt;
&lt;li&gt;[ ] Sending identity is configured&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Authentication
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] SPF configured correctly&lt;/li&gt;
&lt;li&gt;[ ] DKIM configured and verified&lt;/li&gt;
&lt;li&gt;[ ] DMARC configured&lt;/li&gt;
&lt;li&gt;[ ] Legitimate sending sources are documented&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Sending infrastructure
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Sending provider configured&lt;/li&gt;
&lt;li&gt;[ ] Bounce events processed&lt;/li&gt;
&lt;li&gt;[ ] Complaint events processed&lt;/li&gt;
&lt;li&gt;[ ] Suppression system enabled&lt;/li&gt;
&lt;li&gt;[ ] Sending limits understood&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Application
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] From address is controlled&lt;/li&gt;
&lt;li&gt;[ ] Users cannot arbitrarily spoof sender identities&lt;/li&gt;
&lt;li&gt;[ ] Domain verification happens before sending&lt;/li&gt;
&lt;li&gt;[ ] Campaign recipients are managed responsibly&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Monitoring
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;[ ] Delivery rate monitored&lt;/li&gt;
&lt;li&gt;[ ] Bounce rate monitored&lt;/li&gt;
&lt;li&gt;[ ] Complaint rate monitored&lt;/li&gt;
&lt;li&gt;[ ] Domain reputation monitored&lt;/li&gt;
&lt;/ul&gt;




&lt;h1&gt;
  
  
  What We Learned Building This
&lt;/h1&gt;

&lt;p&gt;One of the biggest lessons from building email infrastructure is that &lt;strong&gt;sending an email is the easy part&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The difficult part is building the systems around sending.&lt;/p&gt;

&lt;p&gt;You need to think about:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Identity
Authentication
Infrastructure
Recipient quality
Deliverability
Events
Suppression
Reputation
Monitoring
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A good email platform should hide much of this complexity from the user while still giving them enough visibility and control when they need it.&lt;/p&gt;

&lt;p&gt;That's the direction we're taking with Cresca.&lt;/p&gt;




&lt;h1&gt;
  
  
  Sending Domains Are Now Live in Cresca
&lt;/h1&gt;

&lt;p&gt;We've now added &lt;strong&gt;Sending Domains&lt;/strong&gt; to Cresca so teams can connect their own domains and build their email sending setup around their own brand.&lt;/p&gt;

&lt;p&gt;Instead of treating domain configuration as a separate technical task, it's becoming part of the email workflow itself.&lt;/p&gt;

&lt;p&gt;If you're building a SaaS product, running email campaigns, or sending transactional email, having control over your sending domain is an important foundation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Your domain. Your brand. Your emails.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;You can explore Cresca here:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.cresca.xyz/" rel="noopener noreferrer"&gt;https://www.cresca.xyz/&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Final Thoughts
&lt;/h2&gt;

&lt;p&gt;Email deliverability isn't solved by one DNS record.&lt;/p&gt;

&lt;p&gt;It's a combination of:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Authentication + recipient quality + sending behavior + monitoring + reputation.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Getting the sending domain right is one of the first steps.&lt;/p&gt;

&lt;p&gt;And as your email volume grows, having that infrastructure built into your email platform can save a significant amount of engineering and operational work.&lt;/p&gt;

&lt;p&gt;That's exactly what we're building with Cresca.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>marketing</category>
    </item>
    <item>
      <title>We’ve launched Cresca on Product Hunt! 🚀 Cresca is our AI-powered email marketing tool that helps you create stunning campaigns in seconds — from idea to inbox, no code needed. Please support us by upvoting &amp; sharing 🙏 🔗 https://www.producthunt.com/pro</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Wed, 13 Aug 2025 09:02:25 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/weve-launched-cresca-on-product-hunt-cresca-is-our-ai-powered-email-marketing-tool-that-helps-7dm</link>
      <guid>https://dev.to/crescadotxyz/weve-launched-cresca-on-product-hunt-cresca-is-our-ai-powered-email-marketing-tool-that-helps-7dm</guid>
      <description></description>
      <category>announcement</category>
      <category>productivity</category>
      <category>nocode</category>
      <category>ai</category>
    </item>
    <item>
      <title>How can we grow a Saas</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Tue, 05 Aug 2025 02:10:54 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/how-can-we-grow-a-saas-1nm</link>
      <guid>https://dev.to/crescadotxyz/how-can-we-grow-a-saas-1nm</guid>
      <description></description>
      <category>saas</category>
      <category>startup</category>
      <category>productivity</category>
      <category>career</category>
    </item>
    <item>
      <title>Why I Built Cresca Instead of Using Mailchimp</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Sat, 02 Aug 2025 07:08:22 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/why-i-built-cresca-instead-of-using-mailchimp-4ic8</link>
      <guid>https://dev.to/crescadotxyz/why-i-built-cresca-instead-of-using-mailchimp-4ic8</guid>
      <description>&lt;p&gt;As a technical founder building an AI-native marketing tool, I hit a wall: existing tools like Mailchimp are just too slow, bloated, and manual for the way modern startups operate.&lt;/p&gt;

&lt;p&gt;So I built &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;Cresca&lt;/a&gt; — an AI-native platform to generate, launch, and optimize HTML email campaigns automatically.&lt;/p&gt;

&lt;h3&gt;
  
  
  What Mailchimp gets wrong in 2025:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You still have to manually design and test everything&lt;/li&gt;
&lt;li&gt;Templates are rigid, not personalized&lt;/li&gt;
&lt;li&gt;There’s no feedback loop to improve results over time&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  What Cresca automates:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Email writing from prompts/URLs&lt;/li&gt;
&lt;li&gt;Click tracking, open rate analytics&lt;/li&gt;
&lt;li&gt;AI-powered suggestions and iteration&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can even import your Mailchimp lists to try it.&lt;br&gt;&lt;br&gt;
Try Cresca free — no credit card: &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love feedback from other builders. DM me or comment!&lt;/p&gt;

</description>
      <category>saas</category>
      <category>startup</category>
      <category>ai</category>
      <category>devfounders</category>
    </item>
    <item>
      <title>Newsletter Creation with a Prompt? Meet Cresca.</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Sun, 27 Jul 2025 11:29:35 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/newsletter-creation-with-a-prompt-meet-cresca-33b8</link>
      <guid>https://dev.to/crescadotxyz/newsletter-creation-with-a-prompt-meet-cresca-33b8</guid>
      <description>&lt;p&gt;With Cresca, I just write:&lt;br&gt;
"Send a launch update to users about our new AI model"&lt;br&gt;
And boom — full email, branded, optimized, and inbox-ready.&lt;/p&gt;

&lt;p&gt;This is how email should be: fast, smart, and elegant.&lt;/p&gt;

&lt;p&gt;Built with developers in mind. Try it → &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;/p&gt;

</description>
      <category>emailmarketing</category>
      <category>ai</category>
    </item>
    <item>
      <title>Meet Cresca — The AI Email Agent That Designs Stunning Templates From Just One Prompt</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Sat, 26 Jul 2025 23:56:40 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/meet-cresca-the-ai-email-agent-that-designs-stunning-templates-from-just-one-prompt-1hmn</link>
      <guid>https://dev.to/crescadotxyz/meet-cresca-the-ai-email-agent-that-designs-stunning-templates-from-just-one-prompt-1hmn</guid>
      <description>&lt;p&gt;What Is Cresca?&lt;br&gt;
Cresca is a next-gen, AI-native email marketing platform that automates stunning HTML email template generation — using just one prompt. Built for founders, marketers, and fast-moving teams, Cresca eliminates the painful parts of email design and turns your ideas into polished campaigns in seconds.&lt;/p&gt;

&lt;p&gt;Whether you’re running a startup or scaling your DTC brand, Cresca is the fastest way to go from idea → inbox.&lt;/p&gt;

&lt;p&gt;⚡️ Introducing the Cresca Email Agent&lt;br&gt;
At the heart of Cresca is its AI Email Agent — a powerful assistant that:&lt;/p&gt;

&lt;p&gt;Understands your brand and audience&lt;/p&gt;

&lt;p&gt;Generates high-converting HTML templates&lt;/p&gt;

&lt;p&gt;Refines designs with natural language&lt;/p&gt;

&lt;p&gt;Works with just a single sentence like:&lt;/p&gt;

&lt;p&gt;“Make a modern promotional email for a summer launch with 30% off.”&lt;/p&gt;

&lt;p&gt;No code. No dragging blocks. No fiddling with outdated builders.&lt;/p&gt;

&lt;p&gt;🎨 Beautiful, Responsive Templates — Instantly&lt;br&gt;
Cresca’s templates are:&lt;/p&gt;

&lt;p&gt;Responsive by default&lt;/p&gt;

&lt;p&gt;Built with inline CSS for compatibility&lt;/p&gt;

&lt;p&gt;Styled using your brand colors, fonts, and vibe&lt;/p&gt;

&lt;p&gt;Editable via our live Preview + Edit panel&lt;/p&gt;

&lt;p&gt;Need to tweak the tone, layout, or CTA? Just type a request like:&lt;/p&gt;

&lt;p&gt;“Make it more playful and add a countdown timer.”&lt;/p&gt;

&lt;p&gt;And boom — it’s done.&lt;/p&gt;

&lt;p&gt;🔁 Continuous Refinement Loop&lt;br&gt;
Unlike static builders, Cresca learns from each input. You can:&lt;/p&gt;

&lt;p&gt;Refine your designs endlessly&lt;/p&gt;

&lt;p&gt;Save components and brand profiles&lt;/p&gt;

&lt;p&gt;Generate multiple versions for A/B testing&lt;/p&gt;

&lt;p&gt;Think of it like having a creative email strategist on demand.&lt;/p&gt;

&lt;p&gt;💡 Why We Built Cresca&lt;br&gt;
We were tired of clunky builders and rigid templates. As builders ourselves, we wanted:&lt;/p&gt;

&lt;p&gt;Speed without compromise&lt;/p&gt;

&lt;p&gt;Brand-aligned output without paying an agency&lt;/p&gt;

&lt;p&gt;An AI that understands design and marketing&lt;/p&gt;

&lt;p&gt;That’s how Cresca was born — to empower modern teams with the fastest, smartest way to build marketing emails.&lt;/p&gt;

&lt;p&gt;🚀 Try Cresca (Free Beta)&lt;br&gt;
👉 Visit: &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;br&gt;
You’ll be generating your first email in 30 seconds — no credit card needed.&lt;/p&gt;

&lt;p&gt;We're currently in public beta, and the feedback has been phenomenal. Join hundreds of early adopters who’ve made the switch from clunky tools to Cresca.&lt;/p&gt;

&lt;p&gt;🔍 Why This Matters for Developers and Founders&lt;br&gt;
If you're a dev building internal tools, a marketer running campaigns, or a founder juggling it all — Cresca is built for you.&lt;/p&gt;

&lt;p&gt;No need to integrate 3rd-party builders&lt;/p&gt;

&lt;p&gt;Export clean HTML for any ESP (Mailchimp, Brevo, etc.)&lt;/p&gt;

&lt;p&gt;Use AI to create, test, and launch — all in one place&lt;/p&gt;

&lt;p&gt;💬 Final Thoughts&lt;br&gt;
Cresca is more than a tool — it’s a creative partner.&lt;br&gt;
If you’re serious about email marketing, faster content creation, and beautiful campaigns — you need to try Cresca.&lt;/p&gt;

&lt;p&gt;👉 Try Cresca Now →&lt;br&gt;
Follow us on X &lt;a class="mentioned-user" href="https://dev.to/crescadotxyz"&gt;@crescadotxyz&lt;/a&gt; yz for updates.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>ai</category>
      <category>node</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How I Built an AI Email Platform as a Solo Founder (Cresca Behind the Scenes)</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Wed, 23 Jul 2025 18:18:22 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/how-i-built-an-ai-email-platform-as-a-solo-founder-cresca-behind-the-scenes-1b07</link>
      <guid>https://dev.to/crescadotxyz/how-i-built-an-ai-email-platform-as-a-solo-founder-cresca-behind-the-scenes-1b07</guid>
      <description>&lt;p&gt;Like many founders, I was frustrated by how long it took to write, design, and send emails.&lt;br&gt;
So I built Cresca — a tool that lets you do all of that in seconds using AI.&lt;/p&gt;

&lt;p&gt;Here’s how I went from idea → product → live launch in just a few months.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Problem
Even with modern tools, sending email campaigns felt broken:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Too manual&lt;/p&gt;

&lt;p&gt;Too time-consuming&lt;/p&gt;

&lt;p&gt;Not built for solo makers or small teams&lt;/p&gt;

&lt;p&gt;I wanted to fix that.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The Stack
Frontend: Next.js, Tailwind, Framer Motion&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Backend: Node.js, MongoDB, BullMQ for queues&lt;/p&gt;

&lt;p&gt;AI Layer: OpenAI + prompt engineering&lt;/p&gt;

&lt;p&gt;Infra: AWS + Upstash Redis&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Features I Prioritized
Email generation via prompt&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Campaign scheduling + analytics&lt;/p&gt;

&lt;p&gt;Lightweight UI — fast and clean&lt;/p&gt;

&lt;p&gt;Instant test sends&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Lessons Learned
Launch early, improve fast&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Talk to users, not just code&lt;/p&gt;

&lt;p&gt;Simplicity beats feature bloat&lt;/p&gt;

&lt;p&gt;Feedback is gold — Reddit, Twitter, IndieHackers helped shape v1&lt;/p&gt;

&lt;p&gt;Want to try it?&lt;br&gt;
&lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>programming</category>
      <category>ai</category>
      <category>news</category>
    </item>
    <item>
      <title>Ways to Automate Email Marketing (Without Hiring a Team)</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Tue, 22 Jul 2025 12:33:56 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/ways-to-automate-email-marketing-without-hiring-a-team-j44</link>
      <guid>https://dev.to/crescadotxyz/ways-to-automate-email-marketing-without-hiring-a-team-j44</guid>
      <description>&lt;p&gt;Email marketing works — but it’s often slow, repetitive, and manual.&lt;/p&gt;

&lt;p&gt;If you’re a solo founder or a small team, here are 5 ways you can automate your email marketing strategy and drive real growth without hiring an agency or full-time marketer.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Use AI to Write Emails
Forget staring at a blank screen. Tools like Cresca let you generate complete emails by just typing a short prompt. Example:&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;“Launch announcement for a productivity tool with a 20% discount”&lt;br&gt;
→ Done. Ready to send.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Smart Campaign Templates&lt;br&gt;
Set up evergreen campaigns — onboarding, re-engagement, product updates — once. Use tools that let you store &amp;amp; reuse them dynamically.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Real-Time Analytics&lt;br&gt;
Stop guessing. Use platforms that offer real-time insights into opens, clicks, and engagement — so you can iterate fast.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Drip Sequences for Lifecycle Emails&lt;br&gt;
Welcome → Educate → Convert → Upsell.&lt;br&gt;
Automate the full journey. Cresca supports personalized, prompt-driven sequences too.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Segment Your Audience&lt;br&gt;
Send the right message to the right people. Use tags, behaviors, and time-based filters.&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;🚀 Ready to automate without hiring?&lt;/p&gt;

&lt;p&gt;Try Cresca: &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The Future of Email Marketing is Prompt-Based — Meet Cresca</title>
      <dc:creator>Cresca</dc:creator>
      <pubDate>Tue, 22 Jul 2025 12:32:38 +0000</pubDate>
      <link>https://dev.to/crescadotxyz/the-future-of-email-marketing-is-prompt-based-meet-cresca-1li6</link>
      <guid>https://dev.to/crescadotxyz/the-future-of-email-marketing-is-prompt-based-meet-cresca-1li6</guid>
      <description>&lt;p&gt;Email isn’t dead — it’s evolving.&lt;/p&gt;

&lt;p&gt;In a world of content overload and short attention spans, email remains one of the highest-performing channels in digital marketing. But the tools many of us still use are clunky, slow, and outdated.&lt;/p&gt;

&lt;p&gt;That’s why we built Cresca — an AI-native email marketing platform where you can generate beautifully designed emails and send entire campaigns just by describing what you want in a prompt.&lt;/p&gt;

&lt;p&gt;What’s wrong with traditional email tools?&lt;br&gt;
You spend hours writing and designing&lt;/p&gt;

&lt;p&gt;Automations are overly complicated&lt;/p&gt;

&lt;p&gt;Templates look dated or generic&lt;/p&gt;

&lt;p&gt;Analytics are confusing&lt;/p&gt;

&lt;p&gt;We wanted to rethink that entire process.&lt;/p&gt;

&lt;p&gt;Cresca: AI-Native Email Marketing&lt;br&gt;
With Cresca, you can:&lt;/p&gt;

&lt;p&gt;✅ Generate stunning emails from a simple text prompt&lt;br&gt;
✅ Create campaigns, newsletters, and sequences — fast&lt;br&gt;
✅ Track opens, clicks, and performance in real-time&lt;br&gt;
✅ Save hours on writing, editing, formatting&lt;br&gt;
✅ Automate follow-ups and growth campaigns effortlessly&lt;/p&gt;

&lt;p&gt;Built for:&lt;br&gt;
Founders launching products&lt;/p&gt;

&lt;p&gt;Creators growing communities&lt;/p&gt;

&lt;p&gt;Marketers running lean&lt;/p&gt;

&lt;p&gt;Anyone who hates fiddling with templates&lt;/p&gt;

&lt;p&gt;We're live now. Free plan available.&lt;br&gt;
Try Cresca: &lt;a href="https://cresca.xyz" rel="noopener noreferrer"&gt;https://cresca.xyz&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>ai</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
