The Fundamentals of API Evangelism

About this paper

I’ve had the word “evangelist” over the door since 2010, and for most of those sixteen years the layer it names has been the one practitioners are quickest to wave off as soft, unmeasurable, or marketing’s job. This paper argues the opposite: evangelism is the discipline that decides whether an API is used at all. You can design it perfectly, define it in OpenAPI, deploy it behind a flawless gateway, and govern it to the letter — and it will still sit unused if nobody tells its story, meets developers where they are, and builds a community willing to depend on it.

The headline is the one that closes every honest version of this story: the technology was always the easy part. The paper holds two things at once — storytelling is sacred and it’s the most easily corrupted thing we do — and walks the fundamentals: what evangelism is, internal before external, the blog as the one asset that compounds, outreach and onboarding and community and feedback loops, empathy as a core competency, what you can and cannot measure, and what an agentic audience that can’t be charmed does to all of it. With an anti-patterns list and a self-assessment checklist.

What's inside

1. What API evangelism actually is — the word we keep apologizing for
2. Evangelism vs. advocacy, DevRel, and marketing
3. Belief, then adoption
4. Internal first, external second
5. Why evangelism sits at the end of the Guidance Stack
6. Storytelling is the engine
7. Hacker storytelling — open and machine-readable by default
8. The blog as the compounding asset
9. External evangelism and developer outreach
10. Onboarding as an act of evangelism
11. Be part of your community — don't just sell to it
12. Feedback loops, or it isn't evangelism
13. Empathy as a core competency
14. What you can and cannot measure
15. Anti-patterns — when evangelism becomes theater
16. Self-assessment
17. Where this is going — evangelism in the agentic era

What you get for $25.00