Newsletters are the quiet workhorse of API evangelism — the regular email publication that sustains awareness and engagement over time, reaching people in the one channel almost everyone still checks. In an era obsessed with social media’s reach, email remains the most durable, most direct, and most owned channel an evangelist or an API program has. A newsletter goes straight to the inbox of someone who chose to receive it, unmediated by an algorithm, building a relationship through consistent, valuable presence. I’ve run newsletters, advocated for them, and watched them outlast the social platforms that were supposed to replace them, and my conviction is that the newsletter is one of the most underrated tools in the evangelism toolbox precisely because it’s unglamorous and reliable rather than flashy and ephemeral.
The newsletter’s place in the evangelism toolbox is foundational, and I’ve consistently included it among the core building blocks. When I cataloged the common building blocks of evangelism in 2019, email and newsletters were right there among the fundamental channels — blog posts, social media, talks, and email, each serving a distinct role. The newsletter’s specific role is sustained, periodic, direct engagement: where a blog post reaches whoever finds it and a tweet reaches whoever’s scrolling, a newsletter reaches a committed audience on a regular cadence, in a channel they own and check. In my evangelism toolbox and my personal evangelism algorithm, email is one of the channels through which the storytelling flows. The newsletter isn’t a replacement for the blog or the social presence; it’s the channel that turns occasional readers into a regular audience, the steady drumbeat that keeps an audience engaged between the bigger moments.
My own newsletter history reflects both the value and the discipline the format requires. I finally launched a weekly email newsletter roundup of my posts in 2017, using MailChimp to digest the previous week’s writing and send it out Monday mornings — bringing the steady stream of API Evangelist content to subscribers in a digestible weekly format. I rebooted the API Evangelist newsletter in 2024 via Buttondown, sharing my weekly reading, writing, and projects. And I built free 12-week email knowledge-builder series in 2025, delivering API governance knowledge across topic areas through structured weekly emails. Each of these reflects the same recognition: the newsletter is how you maintain a regular relationship with an audience, and email is a genuinely effective medium for delivering substantive, educational content over time. The 12-week knowledge-builder format especially showed how the newsletter can be more than a roundup — it can be a structured course, an educational sequence, a sustained teaching channel.
The two-directional value of newsletters is something I’ve emphasized from both sides. As a provider and evangelist, the newsletter is how you reach and sustain your audience. But as a consumer, signing up for the newsletters of the API providers you depend on is how you stay informed about their ecosystem. I wrote in 2018 that getting email updates from the API providers I’ve signed up for is one way to stay in tune — because the provider’s newsletter is a signal of platform health and a source of awareness about changes, new features, and the general vitality of the API. Keeping in touch, as I framed it in 2016, is how a provider sets the right tone for an API community, and the newsletter is one of the primary keep-in-touch channels alongside the changelog, the blog, and the support forum. The newsletter works in both directions: it’s how providers stay connected to consumers and how consumers stay connected to providers.
The curation dimension is where newsletters serve the broader community, not just individual programs. I’ve long valued the API newsletters that curate the best of what’s happening across the space — and I wrote in 2025 about the API newsletters that help you learn more about APIs, highlighting the sustained ones like APIs You Won’t Hate, API Developer Weekly, API Changelog, and Net API Notes alongside my own. These curatorial newsletters are a genuine service to the community, filtering the firehose of API news and developments into something a busy practitioner can actually keep up with. My own weekly API.Report and roundup efforts were attempts at this curation — gathering and organizing the most relevant API stories so the community could stay informed. The curatorial newsletter is a form of community service: it requires real work to do well, it’s rarely glamorous, and it provides ongoing value to everyone who relies on it to stay current in a fast-moving field.
The deeper reason I believe in newsletters is that they’re about building an owned audience and a genuine relationship, which is the heart of authentic evangelism. I wrote in 2014 about building the type of audience I really want — a mission-driven audience built through consistent, valuable content rather than chased through pageviews or platform engagement. The newsletter is the purest expression of that: an audience that chose to receive your work, in a channel you own, built through the steady delivery of genuine value. Unlike a social media following, which lives on a platform that can change its rules or disappear, a newsletter audience is yours, a direct relationship not mediated by anyone else’s algorithm or business model. In an evangelism practice built on authenticity and genuine helpfulness, the newsletter is the channel that most embodies those values — no manipulation, no algorithmic gaming, just consistent, valuable content delivered to people who asked for it. That’s why, across fifteen years and many shifts in the channels and platforms of the moment, I’ve kept coming back to the newsletter. It’s the slow, steady, reliable, owned channel that sustains a genuine relationship with an audience over the long term, and in evangelism, that long-term relationship is everything. The flashy channels come and go; the newsletter, and the direct relationship with an audience it represents, endures.
References
- API Evangelism Strategy: Developer Outreach
- API Providers/Consumers Keeping In Touch Is How You Can Set The Right Tone For An API Community
- I Finally Have A Weekly Email Newsletter Roundup Of API Evangelist Posts
- Getting Email Updates From API Providers I Have Signed Up For Is One Way To Stay In Tune
- The Common Building Blocks Of Evangelism
- The API Evangelist Newsletter
- My API Evangelism Toolbox
- The API Newsletter To Help You Learn More About APIs
- API Evangelist Weekly Knowledge Builders Are Now Free And Available Via 12-Week Email Newsletters